Missive + Claude Duet
How to connect Missive to Claude Duet
Set up Missive for Claude Duet with Agent200, then check which tools are available to your agent.
On this page
Overview
This guide connects Missive to Claude Duet through Agent200's MCP server. When you finish, Claude Duet can search, read and act in Missive with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Claude Duet with your Agent200 API key. Your Missive account is connected through managed OAuth: you approve access once on Missive's own page, and Agent200 keeps the connection working.
- Connector
- Missive
- Works with
- Claude Duet ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Missive enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Missive account. They approve access once, on Missive's own page.
- Claude Duet, with custom MCP servers allowed. Claude Duet is a research preview for Pro, Max and Ultra users in the US, by invitation. It uses the connectors of your Claude account, and sending an API key needs Claude's Request headers option.
Connect Missive to Claude Duet
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude Duet in the next step, as "Authorization: Bearer <your key>". One key covers Missive and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Add Agent200 as a custom connector in Claude
Duet has no connector settings of its own: it uses those of your Claude account. In Claude, go to Customize > Connectors, choose Add > Add custom connector, enter the server URL, choose No sign-in and add the
authorizationrequest header withBearerand your key.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
3
Step 3: Use it from Duet
Open Claude Duet with the same Claude account. The connectors set up in Claude are there from your first message; manage them in your Claude settings.
-
4
Step 4: Approve actions when Duet asks
Duet asks before it sends a message, pays, signs or deletes anything. If you cannot approve right away, it finishes the rest and brings the approval back later.
-
5
Step 5: Connect your Missive account
The first time you ask Claude Duet for something in Missive, Agent200 returns an authorization link. Open it and approve access on Missive's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude Duet or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Ask Claude Duet to list the Agent200 tools available for Missive, including which are read-only.
What should come back
- A list of the Missive tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
If no tools appear, check your Agent200 project access for Missive and make sure its tools are enabled. Tool availability depends on your project setup.
Get your API key
Create a key in the Agent200 dashboard. It reaches Missive and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Missive to Claude Duet.
Goal: connect Missive to Claude Duet with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/missive/framework/claude-duet/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude Duet's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Missive is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude Duet: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude Duet's exact menus or commands. 4. The first Missive request returns an authorization link if the user has not connected Missive yet: show it to them and continue once they have approved access on Missive's own page. 5. Check it works with this request: "Ask Claude Duet to list the Agent200 tools available for Missive, including which are read-only." What should come back: - A list of the Missive tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Missive, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/missive/framework/claude-duet.md
Missive tools Claude Duet can call
-
List conversations
Readmissive_list_conversationsList the conversations in the user's inbox.
-
Read a conversation
Readmissive_get_messagesRead the messages in a conversation.
-
Create a draft
Writemissive_create_draftWrite a draft reply in a conversation.
-
Add a post
Writemissive_create_postAdd a post to a conversation for the team to see.
-
List contacts
Readmissive_list_contactsList contacts from the user's contact books.
-
Create a contact
Writemissive_create_contactAdd a new contact to a contact book.
No tool matches that search.
How it works
-
01
You ask Claude Duet
In your own words, for something in Missive.
-
02
Claude Duet picks a tool
It sees the Missive tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Missive connection, within the tools and scopes your project allows.
-
04
Claude Duet answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Missive account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Missive enforces what its API grants.
Troubleshooting
Duet does not see the Agent200 connector
Duet must run on the same Claude account where you added the connector. Check it is listed under Customize > Connectors in Claude.
Scheduled tasks do not call Agent200
Run the task while you are in the conversation. For unattended work, build the agent with the Agent200 SDK.
There is no Request headers option in Claude
Request headers are a Claude beta that only some accounts have, and Duet has no key field of its own. Use Claude Code, or the Agent200 SDK.
Claude Duet shows a Missive authorization link
You have not connected Missive yet, or the connection needs to be approved again. Open the link, approve access on Missive's own page, then ask Claude Duet again.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Missive and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Missive the access the task needs.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Claude Duet's MCP settings, and stop using the old one. Paste the key only into Claude Duet's settings, never into a chat.
