DiscoMCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_targetsA | List target MCP ids configured in this DiscoMCP server. |
| lookup_targetA | Check whether a DiscoMCP skill already covers this target's current declared catalogue, without probing. A MISS (no existing_skill_dir) means dispatch a BACKGROUND subagent to profile the target (inspect_target -> execute_probe gap loop -> finalize_profile) and keep working the user's task while it runs. |
| inspect_targetB | Connect to the target MCP, list its declared tools/resources/prompts, and start a profiling session. Returns tool cards (name, description, input schema, raw server annotations, backstop_blocked advisory) as raw material — YOU classify each tool's risk; DiscoMCP never keyword-guesses. |
| execute_probeA | Validate and, if permitted, execute ONE tool call against the target. DEFAULT-DENY: a probe runs ONLY IF it is provably read-only — a read-verb tool name (list/get/read/search/...), a server readOnlyHint, or a query-executor whose sql/query argument is a read-only statement (SELECT/WITH/SHOW/DESCRIBE/EXPLAIN/PRAGMA). A write-verb tool name or the destructive backstop (server destructiveHint or destructive-verb name) rejects regardless of your declaration. Your |
| finalize_profileA | Synthesize the workspace model, operational model, capability profile, quality report and SKILL.md from this session's accumulated safe observations, and write the full artifact set to disk. VERIFY every claim against the captured observations first — do not assert unobserved structures, identifiers, or relationships (the anti-fabrication provenance check will reject invented observed citations), and mark authored/inferred claims distinctly from probe-observed ones. If ZERO probes were accepted, only a STUB skill is written that plainly states nothing was safely observed — no rich profile is fabricated over a bare catalogue. Pass |
| generate_skillB | Regenerate SKILL.md from an existing profile directory (profile-metadata.json + tool-catalogue.json + workspace-model.json + operational-model.json). |
| session_statusA | Return the current GAP REPORT for an active session, computed only from state already gathered — no target calls, no probe consumed. Reports (does not decide): unsampled_structures (collections listed but never drilled into), unexecuted_tools (unprobed tools minus backstop-blocked; you judge which are read-safe, with why_useful), untraversed_identifiers (ids seen in output but never used as a get-by-id argument, with likely_consumer_tools), sampling_hints (schema params like orderBy/pageSize/q/filter on unused tools for smart sampling), and depth_signal (raw coverage counts + probe budget). The same report rides every execute_probe result under |
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
- 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/ieranama/discomcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server