Claude Code MCP for Cursor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_chatB | Send a message to Claude using Claude Code CLI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool has a clearly distinct purpose.
A single tool named 'claude_chat' follows a consistent verb_noun pattern in snake_case. No inconsistencies exist.
One tool for a chat interaction is too few; typical chat servers would include tools for getting responses, managing history, or configuring context. This feels incomplete for the domain.
The server only offers a 'send message' action. There is no way to retrieve responses, manage conversation state, or clear history, which are obvious gaps for a chat interface.