Adobe + Muse

How to connect Adobe to Muse

Connect Adobe to Muse through Agent200's MCP server: managed OAuth, 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. Adobe tools
  7. How it works
  8. Troubleshooting

Overview

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

You add one MCP server to Muse with your Agent200 API key. Your Adobe account is connected through managed OAuth: you approve access once on Adobe's own page, and Agent200 keeps the connection working.

Connector
Adobe
Works with
Muse ยท Agent app, through MCP
Authentication
Managed OAuth, per end user
Tools
8 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.
  • Adobe enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • An end user with a Adobe account. They approve access once, on Adobe's own page.
  • 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 Adobe 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 Adobe 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"
        }
      }
    }
  5. 5

    Step 5: Connect your Adobe account

    The first time you ask Muse for something in Adobe, Agent200 returns an authorization link. Open it and approve access on Adobe's own page. Agent200 stores the connection and keeps it working; your password never reaches Muse or Agent200.

Test your connection

Run one request to check everything is wired up.

Ask

Send the NDA to jane@acme.com for signature

What should come back

  • An answer built from your own Adobe data.
  • Behind the scenes, Muse calls an Agent200 tool for Adobe, such as adobe_list_agreements.

If Muse shows an authorization link instead, you have not connected Adobe yet: open it, approve access, then ask again.

Get your API key

Create a key in the Agent200 dashboard. It reaches Adobe 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 Adobe to Muse.

Agent brief
Goal: connect Adobe to Muse with Agent200, through its MCP server.
Guide: https://www.agent200.com/tools/adobe/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 Adobe 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. The first Adobe request returns an authorization link if the user has not connected Adobe yet: show it to them and continue once they have approved access on Adobe's own page.
5. Check it works with this request: "Send the NDA to jane@acme.com for signature"
   What should come back:
   - An answer built from your own Adobe data.
   - Behind the scenes, Muse calls an Agent200 tool for Adobe, such as `adobe_list_agreements`.
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 Adobe, then retry.

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

Adobe tools Muse can call

  • Upload a document

    Write
    adobe_upload_document

    Upload a file to use in an agreement.

  • Send for signature

    Write
    adobe_send_agreement

    Send a document to one or more people to sign.

  • List agreements

    Read
    adobe_list_agreements

    List the user's agreements and their status.

  • Get an agreement

    Read
    adobe_get_agreement

    Read an agreement's status and who has or has not signed.

  • Download a signed document

    Read
    adobe_download_agreement

    Download an agreement's document as a PDF.

  • Send a reminder

    Write
    adobe_send_reminder

    Remind the people who still have to sign.

  • Cancel an agreement

    Write
    adobe_cancel_agreement

    Cancel an agreement that is out for signature.

  • List templates

    Read
    adobe_list_templates

    List the reusable documents in the user's library.

How it works

  1. 01

    You ask Muse

    In your own words, for something in Adobe.

  2. 02

    Muse picks a tool

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

  3. 03

    Agent200 runs the call

    With your own Adobe connection, within the tools and scopes 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.

Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Adobe account.

Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Adobe enforces what its API grants.

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 Adobe in the request.

Muse shows a Adobe authorization link

You have not connected Adobe yet, or the connection needs to be approved again. Open the link, approve access on Adobe's own page, then ask Muse again.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Adobe and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Adobe 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 Muse's MCP settings, and stop using the old one. Paste the key only into Muse's settings, never into a chat.

Use Adobe with another framework

200 OK

Adobe, 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)