Think MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| thinkA | Add one evolving reasoning step. Use for iterative work, revisions, or branches. Whole chain ready -> think_batch. Enforced multi-pass gate -> think_cycle. Code-audit checklist -> think_logic. Returns progress, surfaced guidance, and one next action. |
| think_batch | Submit an already-complete reasoning chain atomically. For exploration use think or think_cycle. Rejects thoughts under 50 chars or over 60% similarity; warns when average confidence is below 4. |
| think_doneA | Verify and close a think/think_batch scope before a complex final answer. For think_cycle use action=finalize. Rejects path gaps or unresolved blockers and returns the next correction. |
| think_recallA | Read-only search of an active/explicit scope or saved insights. Use before repeating work or relying on prior reasoning. |
| think_reset | Clear active scope. Irreversible. TRIGGER:
DO NOT RESET:
|
| think_cycleA | Run an enforced multi-pass reasoning loop for high-risk or ambiguous work. Start once, then follow the single returned next step until the gate passes; finish with action=finalize. If start had constraints, include constraintCheck. For ordinary iterative work use think. Do not use think_done for a cycle. Interop:
|
| think_logicA | Return a read-only code-analysis checklist. It does not inspect code, store progress, or produce findings. Use only when a model needs a methodology; use think or think_cycle to perform the analysis. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GofMan5/think-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server