Overview
Claude Code is an AI-powered coding assistant that supports the Model Context Protocol (MCP). Once you’ve generated an MCP server with MCPKit, you can integrate it with Claude Code to give Claude the ability to interact with websites directly from your development environment.Prerequisites
Before you begin, make sure you have:- Claude Code installed (available via VS Code extension or desktop app)
- An MCPKit generated MCP server built and ready to use
- The absolute path to your MCP server’s
dist/index.jsfile
If you haven’t created an MCP server yet, check out our Quickstart Guide to generate your first server in minutes.
Adding Your MCP Server to Claude Code
Step 1: Build Your MCP Server
Navigate to your generated MCP server directory and build it:Verify that the
dist/index.js file was created successfully.Step 2: Add to Claude Code
Use the Claude Code CLI to add your MCP server:your-server-namewith a descriptive name (e.g., “hackernews”, “notion”, “jira”)/absolute/path/to/dist/index.jswith the full path to your built server
Always use absolute paths when configuring MCP servers. Relative paths may not work correctly.
Example
Step 3: Verify Installation
List your configured MCP servers:Using Your MCP Server with Claude
Once configured, you can interact with your MCP server through natural language in Claude Code.Example Interactions
Hacker News Server
Hacker News Server
Project Management Server
Project Management Server
Content Platform Server
Content Platform Server
Managing MCP Servers
List Configured Servers
Remove a Server
Update a Server
To update a server after making changes:-
Rebuild your MCP server:
- The changes will be automatically picked up - no need to re-add the server
If you make significant changes to your MCP server, consider removing and re-adding it to ensure a clean configuration.
Configuration File
Claude Code stores MCP server configurations in:- macOS/Linux:
~/.config/claude/mcp_config.json - Windows:
%APPDATA%\claude\mcp_config.json
Example Configuration
Best Practices
Organize Your Servers
Keep all your MCP servers in a dedicated directory (e.g.,
~/mcp-servers/) for easier managementUse Descriptive Names
Choose clear, descriptive names for your servers that reflect their purpose
Document Your Tools
Add clear descriptions to your MCP tools so Claude understands when to use them
Test Regularly
Use the MCP Inspector to test your servers before integrating with Claude Code
Troubleshooting
Server not appearing in Claude
Server not appearing in Claude
Solutions:
- Verify the server is listed with
claude mcp list - Restart Claude Code
- Check that the path to
dist/index.jsis correct and absolute - Ensure the server built successfully (
npm run build)
Tools not working as expected
Tools not working as expected
Solutions:
- Rebuild your MCP server after any changes
- Check server logs for errors
- Test with the MCP Inspector first:
npx @modelcontextprotocol/inspector node dist/index.js - Verify your Browserbase API key is valid
Authentication issues
Authentication issues
Solutions:
- Ensure you’ve created an authentication context:
mcpkit contexts create yoursite.com - Verify the context exists:
mcpkit contexts list - Try recreating the authentication context if it’s expired
Server crashes or timeouts
Server crashes or timeouts
Solutions:
- Check your Browserbase account for session limits
- Increase timeout values in your MCP server configuration
- Ensure the target website is accessible
- Try reducing the number of concurrent operations
Next Steps
Create More Servers
Generate MCP servers for other websites
Manage Contexts
Save authentication for sites that require login
View Examples
See example MCP servers in action
Advanced Usage
Learn advanced authentication techniques