mcp-metsuke-crunchtools
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METSUKE_DB | No | SQLite database path | ~/.local/share/mcp-metsuke/metsuke.db |
| METSUKE_DB_FILE | No | Path whose contents override METSUKE_DB (container secret-file convention) |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reports_toolA | List all report definitions in the catalog. Returns each definition with its gather prompt, owner agent, schedule, source config, and last-updated time. |
| get_spec_toolA | Return the gather spec (prompt + source config) for a report definition. This is what the autonomous gatherer calls on callback to learn what to collect for the named report. |
| upsert_definition_toolA | Create or update a report definition. The owner_agent field makes the gatherer identity data, not code, so gathering can be re-homed to another agent without a rebuild. |
| save_output_toolA | Persist a gathered report output. The gatherer writes findings here after sweeping the sources. Each finding in payload should carry its own source URL so the compiler can cite it. |
| get_output_toolA | Read a gathered report output for compiling a report. Returns the most recent output by default, or the latest output gathered on a specific date when gathered_date is given. |
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/crunchtools/mcp-metsuke'
If you have feedback or need assistance with the MCP directory API, please join our Discord server