From 789b44ca066920532cbc517ca4f0f779d66f179e Mon Sep 17 00:00:00 2001 From: koladev Date: Mon, 17 Nov 2025 14:08:28 +0100 Subject: [PATCH 1/3] minor fixes --- ...sing-claude-code-with-gram-mcp-servers.mdx | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx index d481705f..713a5df5 100644 --- a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx +++ b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx @@ -55,9 +55,23 @@ 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 prompt you with the required variable names. + +Set the environment variable before restarting Claude Code: +```bash +export MCP_TASK_MASTER_API_KEY='your-api-key-value' +``` + +Alternatively, you can use the `--env-var` flag to specify the environment variable name during installation: +```bash +gram install claude-code --toolset taskmaster --env-var MCP_TASK_MASTER_API_KEY +``` + +#### Configuration Scopes You can control where the MCP server configuration is installed using the `--scope` flag: @@ -211,4 +225,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. - From 48a7549ed09aa8f22e4f38b1e196a82e958788b1 Mon Sep 17 00:00:00 2001 From: tatenda Date: Tue, 18 Nov 2025 10:23:48 +0200 Subject: [PATCH 2/3] spacing --- docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx index 713a5df5..99af5132 100644 --- a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx +++ b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx @@ -62,11 +62,13 @@ This command automatically: If your toolset requires authentication, you'll need to set up environment variables. The `gram install` command will prompt you with the required variable names. Set the environment variable before restarting Claude Code: + ```bash export MCP_TASK_MASTER_API_KEY='your-api-key-value' ``` Alternatively, you can use the `--env-var` flag to specify the environment variable name during installation: + ```bash gram install claude-code --toolset taskmaster --env-var MCP_TASK_MASTER_API_KEY ``` From 1f74365cc64999ae5388cd0f69b4c73edb8cbaf9 Mon Sep 17 00:00:00 2001 From: koladev Date: Tue, 18 Nov 2025 12:22:56 +0100 Subject: [PATCH 3/3] minor changes --- .../using-claude-code-with-gram-mcp-servers.mdx | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx index 99af5132..370a907d 100644 --- a/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx +++ b/docs/gram/clients/using-claude-code-with-gram-mcp-servers.mdx @@ -59,20 +59,14 @@ This command automatically: #### Setting up environment variables -If your toolset requires authentication, you'll need to set up environment variables. The `gram install` command will prompt you with the required variable names. +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. -Set the environment variable before restarting Claude Code: +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' ``` -Alternatively, you can use the `--env-var` flag to specify the environment variable name during installation: - -```bash -gram install claude-code --toolset taskmaster --env-var MCP_TASK_MASTER_API_KEY -``` - #### Configuration Scopes You can control where the MCP server configuration is installed using the `--scope` flag: