Skip to main content

AI SDK Assistant — Claude Code MCP Server Configuration

Quick Setup (All Platforms)

Instead of using the CLI claude mcp add command (which has known issues with spaces in server names), paste the JSON directly into the appropriate config file.
Important: The server name must not contain spaces. Use CRSDK consistently across all configs.

Project Scope — .mcp.json

Create a .mcp.json file in your project root. This is the recommended approach for team collaboration.

macOS / Linux

Windows

On Windows, npx must be wrapped with cmd /c to resolve correctly:
Commit .mcp.json to version control to share with your team.

User Scope — ~/.claude.json (Global)

Available across all projects on your machine.

Finding ~/.claude.json

The ~ refers to your home directory. The full path is: This is a hidden file (starts with .). To see it:
  • macOS Finder: Press Cmd + Shift + . to toggle hidden files
  • Windows Explorer: View → Show → Hidden items
  • Terminal: Open directly with code ~/.claude.json (VS Code) or notepad %USERPROFILE%\.claude.json (Windows)
If the file doesn’t exist, create it and paste the JSON below. Claude Code will pick it up on next launch.

macOS / Linux

Merge into your existing ~/.claude.json (create it if it doesn’t exist):

Windows


Local Scope — .claude.local.json (Private)

Private to the current user and project only. Place this in your project root.

macOS / Linux

Windows


Scope Priority

When the same server is defined in multiple scopes: Local > Project > User

Tool Permissions

To auto-approve all AI SDK Assistant tools, add this to your settings config:
Or approve specific tools only:
Permission config locations:
  • User scope: ~/.claude.json
  • Project scope: .claude/settings.json
  • Local scope: .claude/settings.local.json

Verification

After saving the config, restart Claude Code or start a new session, then run:
You should see:

CLI Alternative

If you prefer using the CLI instead of editing JSON files directly:

macOS / Linux

Windows (PowerShell or CMD)


Troubleshooting