Using Claude Code with Gram-hosted MCP servers

Claude Code  is Anthropic’s terminal-based tool that brings Claude’s capabilities directly to your command line. Unlike Claude Desktop, which runs in a graphical interface, the Claude Code CLI can access your current project folder.

When combined with Model Context Protocol (MCP)  servers, Claude Code becomes even more useful. Using MCP servers, you can give Claude access to your tools and infrastructure, allowing it to work with your APIs, databases, and other services.

This guide shows you how to connect Claude Code to a Gram-hosted MCP server  using Taskmaster, a full-stack CRUD application for task and project management. Taskmaster includes a web UI for managing projects and tasks, a built-in HTTP API, OAuth 2.0 authentication, and a Neon PostgreSQL database for storing data. Try the demo app  to see it in action.

You’ll learn how to set up the connection, test it, and use natural language to manage tasks, projects, and workflows through Claude Code.

Find the full code and OpenAPI document in the Taskmaster repository .

Prerequisites

To follow this tutorial, you need:

• A Gram account 
• Claude Code  installed

Getting started

First, authenticate with Claude Code .

Then, verify that Claude Code is installed correctly:

If installation is successful, you’ll see Claude Code’s available commands and options.

Creating an MCP server

Before connecting Claude Code to a Taskmaster MCP server, you first need to create one. Follow our guide to creating a Taskmaster MCP server.

Connecting Claude Code to your Gram-hosted MCP server

Now let’s connect Claude Code to your Taskmaster MCP server.

To add an MCP server in Claude Code, use the claude mcp add command in your terminal:

• If you’re using the Pass-through Authentication configuration, the JSON configuration looks like this:

  So you can add the server by running the following (replace <your-api-key> with the actual values from your Taskmaster MCP server configuration and your-taskmaster-slug with your MCP server slug):

• Whereas if you’re using the Managed Authentication configuration, the JSON configuration looks like this:

  So you can add the server by running the following (replace <your-gram-api-key> with your actual Gram API key and your-taskmaster-slug with your MCP server slug):

Both configurations use the same commands:

• taskmaster is the name you’ve given the server locally.
• --scope project adds the server to a local .mcp.json file that can be shared with other users on the project. Read more about other scope options  in the Anthropic docs.
• -- separates Claude Code flags from the server command.
• npx mcp-remote is the package that handles remote MCP server connections.
• --header is the flag that passes headers to the remote server.

Verifying the connection

Check that the server was added successfully:

You should see taskmaster in the list.

To see the full configuration, run this command:

Testing the setup

Now test the connection by starting Claude Code and managing some tasks.

First, start an interactive session with Claude Code in your terminal:

Ask Claude a basic question like, “Can you help me create a new task?”

Troubleshooting

Let’s go through some common issues and how to fix them.

Server not found

If Claude Code can’t find your server:

• Check whether the server is listed.

• Remove and re-add the server

Authentication errors

If you get authentication errors:

• Verify your Gram API key in the dashboard under Settings -> API Keys.
• Check that environment variables are correctly set in Gram.
• Ensure the Taskmaster API base URL is accessible.

Tool calls not working

If Claude Code isn’t calling the tools:

• Test the MCP server in the Gram Playground first.
• Check that the toolset includes the tools to use.
• Verify the environment is correctly configured with the required variables.

What’s next

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  and see how easy it is to turn any API into agent-ready tools.