Canopus in your assistant
Ask your assistant how the week went, which campaign brought revenue, or who a contact is, from the place you already work. In your SaaS repository, it also reads your strategy, your ideal customer and your tone, so the copy it writes in your code sounds like your brand.
How it works
Canopus runs a remote MCP server over Streamable HTTP. There is nothing to install: your client connects to one URL.
Every credential is bound to one SaaS. A key or a connector authorized for Edgely reads Edgely, and nothing of your other SaaS.
The server reads and drafts. It never approves, never sends a campaign or a sequence, never deletes. Each answer carries the link to the Canopus screen where you decide.
https://www.canopushq.io/api/mcpClaude Code, with an API key
In the repository of your SaaS, Claude Code connects with an API key.
Create a key
In Canopus, open Settings, then API, and create a key with the Read permission. Copy it: it is shown once.
Store it
Put it in your shell environment as CANOPUS_API_KEY. Never commit it.
Add the server
Run the command below in your repository, then ask Claude for your weekly review.
claude mcp add --transport http canopus https://www.canopushq.io/api/mcp \
--header "Authorization: Bearer $CANOPUS_API_KEY"Claude Desktop and claude.ai, as a connector
Connectors sign in with OAuth: no key to copy, and you choose the SaaS and the permissions on a Canopus screen.
Add a custom connector
In your assistant's settings, open Connectors, add a custom connector and paste https://www.canopushq.io/api/mcp.
Sign in to Canopus
Your assistant opens Canopus. Sign in the way you usually do, two-factor and passkeys included.
Choose the SaaS, then the permissions
Pick the SaaS this connector works on, untick any permission you do not want, and allow. To connect a second SaaS, add the connector again.
Disconnect at any time
In Canopus, Settings, then Connected assistants. The next call of a disconnected assistant is refused.
Other MCP clients
Any client that speaks Streamable HTTP works, with OAuth or with a key in the Authorization header. A typical configuration:
{
"mcpServers": {
"canopus": {
"type": "http",
"url": "https://www.canopushq.io/api/mcp",
"headers": { "Authorization": "Bearer cnp_live_..." }
}
}
}Permissions
A key gets its permissions when you create it; a connector, when you authorize it. A tool you did not grant is not even listed to the assistant.
| Permission | What it allows |
|---|---|
| read | Reports, statistics, revenue, the CRM, the strategy and the calendar. |
| drafts:write | Campaign and sequence drafts, and requests to the content producer and the strategist. |
| contacts:write | Contacts, notes and stages. Sends nothing. |
| events:write | Product events. An event enrols the person in the sequences you approved, so email can leave. |
| transactional:send | Your product emails, through the email API or the assistant. |
Tools
Each tool returns a short summary, the figures behind it, and the link to the matching Canopus screen.
| Tool | What it returns | Permission |
|---|---|---|
| get_weekly_report | The latest weekly report and what waits for your approval. | read |
| get_attributed_revenue | Trials, customers and MRR attributed to campaigns, sequences and sources. | read |
| get_sending_domain_status | Your sending domain: verification, sender, 7-day bounce and complaint rates. | read |
| get_email_quota | Emails sent this month against your plan quota. | read |
| list_campaigns | Your campaigns with their status, filterable. | read |
| get_campaign_stats | One campaign: variants, recipients and its whole funnel. | read |
| list_sequences | Your sequences with their trigger and current enrolments. | read |
| get_sequence_stats | One sequence: steps, enrolments and its funnel. | read |
| search_contacts | Contacts matching an email, a name or a company. | read |
| get_contact | One contact: traits, stage and recent timeline. | read |
| list_audiences | The audiences, formats and sequence triggers a draft can use. | read |
| create_campaign_draft | A campaign in draft, with its messages and an optional B variant. | drafts:write |
| update_campaign_message | Rewrites one message of a campaign not yet approved. | drafts:write |
| add_campaign_message | Adds a message at the end of a campaign not yet approved. | drafts:write |
| add_campaign_variant | Adds a B version of the first message, to test one difference. | drafts:write |
| create_sequence_draft | A sequence in draft: its trigger, its exits and its messages. | drafts:write |
| update_sequence_message | Rewrites one message of a sequence that is not running. | drafts:write |
| add_sequence_message | Adds a message at the end of a sequence that is not running. | drafts:write |
| update_sequence_trigger | Changes what starts and ends a sequence that is not running. | drafts:write |
| request_content_post | Asks the content producer for a post on an angle you give it. | drafts:write |
| request_new_strategy | Asks the strategist for a new strategy version, as a draft. | drafts:write |
| upsert_contact | Creates a prospect, or updates the contact with this email. Product facts are refused. | contacts:write |
| add_contact_note | Adds a note to the timeline of a contact. | contacts:write |
| move_contact_stage | Moves a prospect to a stage of the pipeline. A stage that makes them a customer is refused: the founder converts in Canopus. | contacts:write |
| track_product_event | A product event (signup, trial, plan change, churn) on the same path as the CRM webhook. | events:write |
| send_transactional_email | One product email to one address, like POST /api/v1/emails. | transactional:send |
| get_transactional_email | The delivery status of a transactional email. | transactional:send |
Resources
Context your assistant reads before it writes anything for your SaaS.
| Resource | What it holds |
|---|---|
| canopus://strategy | The strategy in force: positioning, segments, channels, objective. |
| canopus://icp | Your ideal customer profile and its segments. |
| canopus://tone | Your tone of voice, with writing samples. |
| canopus://product-brief | What Canopus learned about your product. |
| canopus://calendar | The content calendar of the next six weeks. |
| canopus://email-api | The transactional email API reference, for the transactional:send permission. |
Prompts
Ready-made tasks your assistant offers in its prompt menu.
| Prompt | What it does |
|---|---|
| weekly_review | The week in a few lines, what waits for you, and the next step. |
| onboarding_audit | Your sign-up flow in the code, compared with the sequences Canopus runs. |
| announce_feature | What you shipped, read from the code, turned into a campaign draft, an activation sequence and a post. |
What the assistant can never do
- Approve anything, or send a campaign or a sequence. Those tools do not exist, so a page or a file your assistant reads cannot talk it into using them.
- Delete or purge data.
- Change a sequence that is running or a campaign that is sending. Those edits are yours, in Canopus.
- Reach another SaaS than the one its credential is bound to.
- Keep access after you revoke the key or disconnect the connector.
Limits
- 60 calls per minute per key or connector, apart from the email API.
- The MCP server is part of every paid plan. A SaaS without an active subscription cannot be connected, and its keys and tokens are refused with an explanation and no data.
- Every call is recorded in the audit log with the key or connector that made it.