AgentMail + Muse

How to connect AgentMail to Muse

Connect AgentMail to Muse through Agent200's MCP server: no separate key, ready-made tools and one API key.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. AgentMail tools
  7. How it works
  8. Troubleshooting

Overview

This guide connects AgentMail to Muse through Agent200's MCP server. When you finish, Muse can search, read and act in AgentMail with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Muse with your Agent200 API key. AgentMail is reached with that key, so there is no separate AgentMail key to manage.

Connector
AgentMail
Works with
Muse ยท Agent app, through MCP
Authentication
Your Agent200 API key
Tools
7 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.
  • AgentMail enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • Muse, with custom MCP servers allowed. Muse creates custom connectors from a chat, and your key goes into its secure credentials sheet, never into the chat. Muse Code reads servers from its settings file.

Connect AgentMail to Muse

  1. 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 Muse in the next step, as "Authorization: Bearer <your key>". One key covers AgentMail and every other connector enabled for your project. Keep it out of chats and source control.

  2. 2

    Step 2: Ask Muse to create a custom connector

    Start a new Muse chat and send this message. Muse builds the connector and shows a button to add your API key.

    Muse chat
    MCP: message that asks Muse to create the custom connector
    Create a Custom Connector for the Agent200 remote MCP server and connect to it:
    Name: Agent200
    Transport: remote streamable HTTP
    URL: https://api.agent200.com/mcp/
    Auth: API key sent in the Authorization header as "Bearer <key>"
    Open the secure credentials store so I can enter the API key there, not in this chat.
    Then list its tools to confirm the connection works.
  3. 3

    Step 3: Add your key in the secure sheet

    Tap the button Muse shows to open Add custom connector, paste your Agent200 API key and tap Add. Muse keeps it in its Secure Credentials Store and lists the Agent200 tools once the connection works.

  4. 4

    Step 4: Using Muse Code? Add the server to its settings

    In the terminal version, declare the server in ~/.config/muse/settings.json and export AGENT200_API_KEY in your shell instead of writing the key in the file. Run /mcp in a session to see it.

    ~/.config/muse/settings.json
    MCP: Muse Code settings.json entry
    {
      "schema_version": 1,
      "mcp_servers": {
        "agent200": {
          "transport": "streamable_http",
          "url": "https://api.agent200.com/mcp/",
          "headers": { "Authorization": "Bearer ${AGENT200_API_KEY}" },
          "enabled": true,
          "mode": "optional"
        }
      }
    }

Test your connection

Run one request to check everything is wired up.

Ask

Check the support inbox for new messages

What should come back

  • A result from AgentMail, returned through your Agent200 API key.
  • Behind the scenes, Muse calls agentmail_list_inboxes.

If a tool is refused, check that AgentMail is switched on for your project in the Agent200 dashboard.

Get your API key

Create a key in the Agent200 dashboard. It reaches AgentMail and every other connector enabled for your project.

Read the SDK docs

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 AgentMail to Muse.

Agent brief
Goal: connect AgentMail to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/agentmail/framework/muse/

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 Muse's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure AgentMail is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Muse: 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 Muse's exact menus or commands.
4. Check it works with this request: "Check the support inbox for new messages"
   What should come back:
   - A result from AgentMail, returned through your Agent200 API key.
   - Behind the scenes, Muse calls `agentmail_list_inboxes`.
5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The whole guide is also available as Markdown, for agents and LLMs: /connectors/agentmail/framework/muse.md

AgentMail tools Muse can call

  • Create an inbox

    Write
    agentmail_create_inbox

    Create a new email inbox for the agent.

  • List inboxes

    Read
    agentmail_list_inboxes

    List the agent's inboxes.

  • Send a message

    Write
    agentmail_send_message

    Send an email from an inbox.

  • List messages

    Read
    agentmail_list_messages

    List the messages in an inbox.

  • Read a message

    Read
    agentmail_get_message

    Read a message and its content.

  • Reply to a message

    Write
    agentmail_reply_to_message

    Reply to a message in its thread.

  • List threads

    Read
    agentmail_list_threads

    List the email threads in an inbox.

How it works

  1. 01

    You ask Muse

    In your own words, for something in AgentMail.

  2. 02

    Muse picks a tool

    It sees the AgentMail tools on the Agent200 MCP server and calls the one the request needs.

  3. 03

    Agent200 runs the call

    It reaches AgentMail with your Agent200 API key, within the endpoints your project allows.

  4. 04

    Muse answers

    It gets the result back from the MCP server and uses it in its reply or its next step.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

You pasted the API key into the chat

Create a new key on the API keys page, stop using the old one, and enter the new one only through the secure Add custom connector sheet. Keys typed in a chat stay in its history.

Muse returns unauthorized when it lists the tools

Ask Muse to update the Agent200 connector’s credential and enter the key again in the secure sheet. Say that it goes in the Authorization header with the Bearer prefix.

Muse asks for a local command or a package

Answer that Agent200 is a hosted server over remote streamable HTTP, with API key sign-in. Nothing has to be installed.

Muse does not use Agent200 in a later chat

Start a new chat after connecting, and name Agent200 and AgentMail in the request.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that AgentMail and the tools you need are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, replace it in Muse's MCP settings, and stop using the old one. Paste the key only into Muse's settings, never into a chat.

Use AgentMail with another framework

200 OK

AgentMail, connected to Muse.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)