Skip to main content
The emma MCP Server gives any MCP-compatible client — Cursor, Claude Code, Codex, and others — programmatic access to emma’s integration ecosystem and Skill library, without exposing hundreds of individual tools to your agent’s context window. Instead of registering a separate MCP tool for every Slack action, every GitHub action, every Notion action, and so on, emma follows a Tool Vendor pattern (similar to Composio): a small number of meta-tools let your agent search for the right integration, inspect its schema, and execute it on demand. A parallel Skill Vendor pattern does the same for reusable, saved workflows.

​
Features

Tool Discovery

Search across emma’s integrations (Slack, GitHub, Notion, Gmail, and more) by keyword instead of memorizing tool names

Direct Execution

Execute any discovered tool with structured arguments and get the result back inline

Built-in OAuth Handling

When a tool needs authentication, you get a connect link back automatically — no separate auth flow to build

Skill Library

Save a workflow once and reuse it from any machine, IDE, or agent — Skills are stored in emma’s cloud

Health Monitoring

Verify your API key and connection before running anything else

​
Authentication

The emma MCP Server requires an API key for authentication.

​
Getting Your API Key

  1. Log in to emma
  2. Go to API Keys
  3. Create or copy your API key
Send it with every request as Authorization: Bearer <api_key> (or X-API-Key: <api_key>). See the Setup Guide for the exact client configuration.
Keep your API key secure. Do not commit it to version control or share it publicly.

​
Available Tools

The emma MCP Server provides 9 tools organized into three categories:

​
Health Check

​
Tool Vendor

​
Skill Vendor

For detailed parameters, response formats, and examples for every tool, see the Tools Reference.

​
Tool Vendor: search → schema → execute

1

Search for a tool

Call emma_search_tools with a natural-language query (optionally filtered by service) to find the right integration tool name.
2

Inspect its schema (if needed)

Call emma_get_tool_schema with the exact tool name to see its required and optional arguments.
3

Execute it

Call emma_execute_tool with the tool name and a JSON object of arguments. If the underlying service requires authentication you haven’t set up yet, the response includes a connect_link — visit it, then retry.

​
Skill Vendor: list → get → follow → save

1

Check for an existing Skill

Call emma_list_skills before starting a task — it returns all your saved Skills (optionally filtered by query) with pagination.
2

Read its instructions

Call emma_get_skill with a skill_id to get the full step-by-step instructions.
3

Follow the instructions

Your agent executes the steps itself, using emma_search_tools / emma_execute_tool for any integration actions along the way.
4

Save new workflows

Once you’ve built a workflow worth reusing, call emma_create_skill so it’s available from any machine or agent later.

​
Use Cases

​
Discover and use an integration from your IDE

Your agent will call emma_search_tools, then emma_execute_tool (fetching the schema first if it’s unsure of the arguments).

​
Handle authentication mid-task

If you haven’t connected Slack yet, emma_execute_tool returns success: false with reason: "auth_required" and a connect_link. Your agent should surface that link, wait for you to authenticate, then retry the same call.

​
Save and reuse a workflow as a Skill

Skills created this way also appear in emma’s Web UI under the Skills tab and can be used by emma’s own agents — not just your MCP client.

​
Next Steps

Setup Guide

Configure the emma MCP Server in Cursor, Claude Code, or Codex

Tools Reference

Detailed documentation for all tools