Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,19 @@ gram install claude-code --toolset taskmaster
This command automatically:
- Fetches your toolset configuration from Gram
- Derives the MCP URL and authentication settings
- Creates the correct configuration (by default in user-level `~/.claude/settings.local.json`)
- Creates the correct configuration (by default in user-level `~/.claude.json`)

**Configuration Scopes:**
#### Setting up environment variables

If your toolset requires authentication, you'll need to set up environment variables. The `gram install` command will display the required variable names and provide the export command you need to run to set the variable value.

For the Taskmaster toolset, you'll need to set the `MCP_TASK_MASTER_API_KEY` environment variable to your Taskmaster API key. You can do this by running the following command:

```bash
export MCP_TASK_MASTER_API_KEY='your-api-key-value'
```

#### Configuration Scopes

You can control where the MCP server configuration is installed using the `--scope` flag:

Expand Down Expand Up @@ -211,4 +221,3 @@ If Claude Code isn't calling the tools:
You now have Claude Code connected to a Gram-hosted MCP server with task management capabilities.

Ready to build your own MCP server? [Try Gram today](/product/gram) and see how easy it is to turn any API into agent-ready tools.

Loading