Agents MCP Server

Model Context Protocol (MCP) Server for the *@inkeep/agents-mcp* API.

Local serverstdioTypeScript

What is the Agents MCP server?

Most developer tooling work still happens through a UI a human drives. Agents MCP server moves it into the conversation instead. Model Context Protocol (MCP) Server for the @inkeep/agents-mcp API.

The short version

Build AI Agents with a No-Code Visual Builder or TypeScript SDK. Agents can be edited in either with full 2-way sync, so technical and non-technical teams can create and manage Agents in one platform.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 6 tools. What each one is for:

  • Multi — agent architecture to support teams of agents
  • agents-api — An API that handles configuration of Agents, Sub Agents, MCP Servers, Credentials, and Projects with a REST API. Additionally, it exposes Agent
  • agents-manage-ui — Visual Builder web interface for creating and managing Agents. Writes to the agents-api
  • agents-sdk — TypeScript SDK (@inkeep/agents-sdk) for declaratively defining Agents and custom tools in code. Writes to agents-api
  • agents-cli — Includes various handy utilities, including inkeep push and inkeep pull which sync your TypeScript SDK code with the Visual Builder
  • agents-ui — A UI component library of chat interfaces for embedding rich, dynamic conversational AI experiences in web apps

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Agents's toolset — Multi, agents-api, agents-manage-ui and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agents's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Multiagent architecture to support teams of agents
agents-apiAn API that handles configuration of Agents, Sub Agents, MCP Servers, Credentials, and Projects with a REST API. Additionally, it exposes Agent execution and evaluation. The API tracks conversation state and emits OTEL t
agents-manage-uiVisual Builder web interface for creating and managing Agents. Writes to the agents-api.
agents-sdkTypeScript SDK (@inkeep/agents-sdk) for declaratively defining Agents and custom tools in code. Writes to agents-api.
agents-cliIncludes various handy utilities, including inkeep push and inkeep pull which sync your TypeScript SDK code with the Visual Builder.
agents-uiA UI component library of chat interfaces for embedding rich, dynamic conversational AI experiences in web apps.

Example prompts to try

  • Use Agents to Multi.
  • Use Agents to agents-api.
  • Use Agents to agents-manage-ui.

Frequently asked questions

It connects Agents to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Multi, agents-api, agents-manage-ui, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agents directly.