Agents

Developer MCP vs listed agent

Two ways to connect AI to Artmail — your org API key, or a marketplace catalog agent

Developer MCP vs listed agent

Artmail supports two different “connect an agent” stories. They use different credentials, permissions, and docs. Pick the row that matches what you are building.

Which one am I?

Developer MCP (API key)Listed catalog agent (marketplace)
You areA user connecting Claude, Cursor, or another MCP client to your Artmail organizationA builder who publishes a third-party agent for brands to discover and activate
CredentialA developer API key you create in Dashboard → Developers → API keysA scoped key provisioned by Artmail when a brand activates your listing — delivered once via webhook + your server
Typical toolsEmail send, contacts, campaigns, templates, automations — depending on scopes you chooseGrowth and orchestration inside the agent platform: landing pages, lead magnets, forms, brand context, runs, approvals — not bulk email from the agent
Send email?Can, if the key includes transactional:send (and related scopes)No — listed agents do not receive send permissions and do not read contact PII
DocsConnect your agent (this is the MCP setup for your org)Publish your agent, Webhook events

Mental model

  • Developer MCP = your automation and copilots against your account, with a key you control.
  • Listed agent = your product running inside each customer’s workspace, with keys and scopes Artmail issues per activation.

The agent builder marketing site and the agent pricing FAQ describe the marketplace / catalog path. Connect your agent describes the developer API key path.

Connect your agent

MCP install for Claude, Cursor, and other clients using ARTMAIL_API_KEY.

Connect your agent →

Publish your agent

Listing, webhooks, and activation for third-party agents in the directory.

Publish your agent →