Using MCP from Another Project

mapular install wires the MCP servers into the directory you run it from. If you want to use them from a different project, run the same command pointing at that project's path.

Add MCP to another project

mapular install --for /path/to/your/project

This does two things:

1. Writes server definitions into that project's .mcp.json
2. Approves the servers in ~/.claude.json under projects.<path>.enabledMcpjsonServers

Both steps are required. Without step 2, Claude Code silently ignores servers in .mcp.json even if the file is present.

Manual setup

If you prefer to configure things by hand, add this to the project's .mcp.json:

{
  "mcpServers": {
    "mapular-mpoi-mcp": {
      "command": "uvx",
      "args": ["mapular-mpoi-mcp"]
    },
    "mapular-geo-mcp": {
      "command": "uvx",
      "args": ["mapular-geo-mcp"]
    },
    "mapular-admin": {
      "command": "uvx",
      "args": ["mapular-admin-mcp"]
    }
  }
}

Then add to ~/.claude.json:

{
  "projects": {
    "/absolute/path/to/your/project": {
      "enabledMcpjsonServers": [
        "mapular-mpoi-mcp",
        "mapular-geo-mcp",
        "mapular-admin"
      ]
    }
  }
}

Restarting Claude Code

After changing any MCP config, restart Claude Code properly:

• VS Code: Close the Claude Code panel and open a new conversation (+ button or Cmd+Shift+P → "Claude Code: New Conversation")
• CLI: Exit with Ctrl+C, then run claude again

Pressing Enter in an existing chat does not reload server config.

VS Code multi-root workspaces

Claude Code uses the first workspace folder as its working directory. If that folder does not have the servers configured, they will not load — even if another folder in the workspace does. Run mapular install --for on whichever folder is listed first in your .code-workspace file.

Verify

Type /mcp in any Claude Code conversation. All three servers should appear as connected.