Connect an agent with a personal key

Before you start

Prerequisites

An active account and an MCP client that supports authenticated HTTP servers.

Permissions and plan

Personal keys inherit their owner's access. A key does not bypass organization permissions.

Steps

1. Open MCP setup and sign in. You return to /mcp to manage personal keys. Store a new key privately; it is shown once.

2. Configure a compatible client with the Streamable HTTP endpoint and a Bearer header using its private secret mechanism.

3. Use Copy verification prompt to ask the connected agent to discover tools and call list_diagrams without modifying data. An empty list is a successful connection.

4. Give your agent an existing diagram link, or ask it to create one model, retain the ID and use get_diagram to verify its content. Discover exact shapes through list_shapes.

5. Open the returned /app?diagram=ID link in the desktop editor. Reuse that same ID for patch_diagram and subsequent checks; do not create another diagram for every edit.

Copy this model into Import in the editor. Export current work first. The two stable identifiers, api and db, connect the services to the flow.

# Request path

- API {#api type=service x=100 y=120}
- Database {#db type=database x=500 y=120}

## Flows
- api -> db {#requests label="requests" color=#f05a47 speed=1 direction=forward}

Change a label to describe your system. Keep the identifiers the same when you want existing connections to keep referring to those nodes.

Check your work

Expected outcomeYour agent can discover shapes and work with an authorized diagram.

Next steps

Try the workflow in the editor, then use the reference for control details and model syntax.

If a step does not work, keep an export of your model and follow the troubleshooting guide. Include the error message when contacting support, without sharing credentials or private architecture.