Canopy account

com.canopy-ioPublished by canopy-io.comOfficial publisherv1.0.0Updated Nov 1, 2026

Every Canopy public API operation as a tool, run as you after a browser sign-in or on an API key.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote Canopy MCP endpoint that exposes every Canopy public API operation as a tool, acting as the signed-in user or an API key.

What you can do
  • Run any Canopy public API operation as a tool, acting as the signed-in user.
  • Sign in through the browser, or authenticate with a Canopy API key when no browser is available.
  • Scope each tool's permissions through the API key's scopes.
When to use it
Use it when you want an assistant to work with Canopy's public API on your behalf, either interactively after a browser sign-in or from a client that cannot open a browser and uses an API key instead.
Requirements
A remote streamable HTTP endpoint at auth.canopy-io.com; no local package or runtime. OAuth sign-in in a browser is required, or an X-API-Key header for clients that cannot open a browser. Network access to the endpoint.
Before you install
The server acts as you, so tools can perform whatever the Canopy API allows, including operations that write or change data. An API key is a secret sent in the X-API-Key header; its scopes decide what each tool may do, so grant only what is needed. No tool list is published, so review the available operations before use.

Installation

In SourceWeft

  1. Open Canopy account in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.canopy-io%2Faccount/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "canopy-account": {
      "type": "http",
      "url": "https://auth.canopy-io.com/mcp/v1"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 1, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Canopy-Io integrations