> Source: https://builder.ema.ai/v2/ema-mcp/capabilities
> Title: Capabilities

# Capabilities

You drive the Ema MCP with plain language. You describe what you want, and your assistant picks the right tool and calls it on your behalf — reading data, making a change, or chaining several steps together. This page groups what's available by area, with example prompts.

You don't need to know tool names. To see exactly what your assistant can do, ask "What Ema tools do I have access to?" or open the MCP view in your client (for example, `/mcp` in Claude Code or Codex). The exact set of tools depends on your role and tenant, and grows over time.

## What you can do

Area

What you can do

Example prompt

AI Employees

List and inspect AI Employees, create one from a template, from scratch, or by cloning, update configuration, set the EmaFusion™ model, and archive or restore.

"Create a Chat AI Employee called IT Support."

Workflows

Inspect an AI Employee's workflow, edit the graph (add or remove nodes, edges, agents, Tools, and knowledge bases), validate it, do a dry run, and publish a new version.

"Show me the workflow for the Sales Assistant AI Employee."

Knowledge bases

Create and list knowledge bases, upload and remove documents, search them, and manage data connections and sync.

"Upload this PDF to the Support knowledge base."

Integrations & Tools

Browse the integrations catalog, create and configure Tools, manage connections (including OAuth), and validate or invoke a Tool.

"Show me available integrations and add a Tool to the Sales Assistant AI Employee."

Chat & testing

Start a chat session with an AI Employee, send messages, and review message history — useful for testing behavior.

"Send a test message to the HR AI Employee and show me the reply."

Dashboards

List dashboard tables and rows, upload a file, create and rerun rows, and read results.

"Upload this spreadsheet to the Invoice dashboard and run it."

Human in the loop

View pending human-in-the-loop requests, respond to them, and cancel them.

"Show me any approvals waiting on me."

Models

List the models available to your tenant through EmaFusion™.

"Which models can I use?"

Debugging

Inspect recent runs and conversations to see what happened and why a step failed.

"What went wrong in the last conversation with the HR AI Employee?"

Identity

Confirm who you're signed in as and which tenant you're working in.

"Who am I on Ema?"

For background on the concepts these actions operate on, see [AI Employees](/builder/v2/core-concepts/ai-employees), [Workflows](/builder/v2/core-concepts/workflows), and [Knowledge bases](/builder/v2/core-concepts/knowledge-bases).

## Reading versus changing

Some requests only read data — listing AI Employees, showing a workflow, inspecting a conversation. Others change your tenant: creating, updating, publishing, or deleting. The MCP makes these changes as you, so they take effect immediately and are subject to the same permissions as the rest of the platform.

> [WARNING]
> **Review actions that change or delete.** Creating, updating, publishing, archiving, and deleting are real changes to your tenant — for example, archiving an AI Employee takes it out of service, and deleting a knowledge base, Tool, or connection is permanent. Most MCP clients ask you to confirm before running a tool that makes a change; read what the assistant proposes before you approve it. When you want to try something safely, connect to the Dev or Staging environment rather than Prod.

## Scope and permissions

The connection always acts as the signed-in user, within one tenant and environment:

-   **Your role decides what you can do.** Building and publishing AI Employees requires builder access. If your role doesn't permit an action, the request is refused — the MCP can't elevate your access.
-   **Tenant isolation.** You only see and change resources in the tenant you signed in to. Resources in other tenants aren't visible.
-   **One environment at a time.** A connection is pinned to the environment you set it up with. To act on a different environment, use that environment's connection.

For the full permission and role model, see [Governance and Permissions](/builder/v2/administration/governance-and-permissions).

## What's next

-   [Setup](/builder/v2/ema-mcp/setup) — connect a client if you haven't yet.
-   [Troubleshooting and Limits](/builder/v2/ema-mcp/troubleshooting-and-limits) — fix issues and understand the limits.
-   [Autopilot](/builder/v2/autopilot) — the same capabilities, inside the Ema product.