Connecting Claude
Wire Claude Desktop or Claude Code to your Jaina MCP server.
Prerequisites
- A Jaina API token. Get one at
/settings/tokens→ Create token. - Claude Desktop or Claude Code installed.
Claude Desktop
Edit your config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add:
{
"mcpServers": {
"jaina": {
"url": "https://jaina.dev/api/mcp",
"auth": {
"type": "bearer",
"token": "jn_live_..."
}
}
}
}
Restart Claude Desktop. A "Jaina" entry appears in the MCP tools panel.
Claude Code
In ~/.claude/settings.json:
{
"mcp": {
"servers": {
"jaina": {
"url": "https://jaina.dev/api/mcp",
"auth": {
"type": "bearer",
"token": "jn_live_..."
}
}
}
}
}
Run /mcp restart (or restart Claude Code).
First test
In a Claude conversation:
List my Jaina projects.
Claude calls jaina_list_projects and prints the result.
Show me the schemas in my-game.
Claude calls jaina_list_schemas with project_slug: "my-game".
Token rotation
Best practice: rotate tokens quarterly. To rotate:
- Generate a new token at
/settings/tokens. - Update your config file.
- Restart Claude.
- Revoke the old token.
Troubleshooting
The Jaina entry doesn't appear. Verify the JSON is valid. Look for syntax errors. Restart Claude completely (not just reload).
Tools are listed but calls fail with 401. The token is invalid or revoked. Generate a new one.
Calls hang. Network issue between your machine and jaina.dev. Check curl https://jaina.dev/api/v1/projects -H "Authorization: Bearer jn_live_..." from the same machine.
Tools work but Claude doesn't use them. Be explicit: "Use the jaina MCP tools to list my projects."
