Canopy documentation is an MCP server published by com.canopy-io, hosted at canopy-io.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including list_surfaces, find_surface, get_guide, explain_capability, search_api.
Answers questions about the Canopy dashboards and API from the published docs. No sign-in.
4 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Every left-nav page of both signed-in applications: the application, the menu path in the labels on screen, the capability that opens it, what must be selected first, and the guide that walks through it. The same data as /ai/ui-map.json.
| Parameter | Type | Description |
|---|---|---|
| application | string | Limit to one application. |
{
"name": "list_surfaces",
"title": "List every page of the Developer Console and Admin Workspace",
"description": "Every left-nav page of both signed-in applications: the application, the menu path in the labels on screen, the capability that opens it, what must be selected first, and the guide that walks through it. The same data as /ai/ui-map.json.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"application": {
"enum": [
"Developer Console",
"Admin Workspace"
],
"type": "string",
"description": "Limit to one application."
}
}
},
"annotations": {
"readOnlyHint": true
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Given what someone wants to do ("rotate a webhook secret", "invite an administrator", "why can't I see Hierarchy"), return the pages where it happens, ranked, each with its menu path, the capability that opens it, and its guide.
| Parameter | Type | Description |
|---|---|---|
| query * | string | What the person wants to do, in their words. |
{
"name": "find_surface",
"title": "Find where something is done in the dashboards",
"description": "Given what someone wants to do (\"rotate a webhook secret\", \"invite an administrator\", \"why can't I see Hierarchy\"), return the pages where it happens, ranked, each with its menu path, the capability that opens it, and its guide.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"minLength": 2,
"description": "What the person wants to do, in their words."
}
}
},
"annotations": {
"readOnlyHint": true
}
}A docs page as markdown: for a dashboard guide, the menu path, the exact controls to click in order, and the reasons a control may be missing. Pass the guide URL or path from find_surface or list_surfaces, or a surface id such as console.roles.
| Parameter | Type | Description |
|---|---|---|
| page * | string | A docs URL, a /docs/... path, or a surface id. |
{
"name": "get_guide",
"title": "Read a guide",
"description": "A docs page as markdown: for a dashboard guide, the menu path, the exact controls to click in order, and the reasons a control may be missing. Pass the guide URL or path from find_surface or list_surfaces, or a surface id such as console.roles.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"page"
],
"properties": {
"page": {
"type": "string",
"description": "A docs URL, a /docs/... path, or a surface id."
}
}
},
"annotations": {
"readOnlyHint": true
}
}What a capability such as env_roles.manage or billing.manage lets someone do, and which pages it opens. The answer to "why can't I see this button": a page shows only for someone holding one of its listed capabilities, and its write actions only for the matching manage capability.
| Parameter | Type | Description |
|---|---|---|
| capability * | string | A capability key, e.g. env_roles.view. |
{
"name": "explain_capability",
"title": "Explain an administrator capability",
"description": "What a capability such as env_roles.manage or billing.manage lets someone do, and which pages it opens. The answer to \"why can't I see this button\": a page shows only for someone holding one of its listed capabilities, and its write actions only for the matching manage capability.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"capability"
],
"properties": {
"capability": {
"type": "string",
"description": "A capability key, e.g. env_roles.view."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Search the published OpenAPI documents by words from the task or the resource. Returns method, path, operation id, and the reference page for each match. Reference pages live at /docs/api-reference/{operationId}; never guess those URLs.
| Parameter | Type | Description |
|---|---|---|
| query * | string |
{
"name": "search_api",
"title": "Find the API operation behind a task",
"description": "Search the published OpenAPI documents by words from the task or the resource. Returns method, path, operation id, and the reference page for each match. Reference pages live at /docs/api-reference/{operationId}; never guess those URLs.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"minLength": 2
}
}
},
"annotations": {
"readOnlyHint": true
}
}Names, descriptions and schemas were written by the server and are shown as data.