Skip to content
Merulan

MCP

Use MCP tool discovery to give an agent bounded access to admitted Merulan operations.

MCP is in Preview. It declares two tools. search_docs finds public docs. execute runs an admitted command when the gateway is available. The production gateway is hibernated. Neither tool can run there now.

Support: support@merulan.com. Security reports: security@merulan.com. No package or live-service availability is claimed.

Set up access

You cannot connect to the public production gateway while it is hibernated. Do not treat https://mcp.merulan.com/mcp as an available endpoint yet. When Merulan marks the gateway available, configure that URL in an MCP client and use the published MCP authentication flow. An MCP token has an audience and scope. The server checks live membership before a tool runs. Confirm the agent has the intended Workspace. Keep credentials with the agent runtime, out of prompts and shared configuration. Do not substitute an API credential for an MCP token.

How the MCP works

MCP offers search_docs and execute. Start with search_docs to find a Capability or doc id. Then call execute with a command name and arguments. The gateway checks that command's permission at call time. It does not grant one broad tool permission.

Use search_docs({}) to list docs when you do not know an id. The MCP reference owns the two tool signatures. An HTTP method's presence does not prove that MCP admits its command.

First call

Use search_docs to find Runs and lineage. Read the guide before choosing a command. Use a Run id from an allowed Console readback, then follow execute with the admitted command and its arguments. Compare the returned Run identity and status with the Console. Keep the tool call id for follow-up. A tool call alone is not success.

When it fails

MCP arguments are invalid

The arguments do not match the command schema. Check the tool signature and the selected command's input contract. Correct the input before making a new call.

not_found

The requested doc id is outside the published manifest. Call search_docs({}) or search by a Capability name. Use a returned id rather than inventing one.

Deployment unavailable

The production gateway is hibernated. Wait for an availability notice and a supported authentication path. A local tool response cannot qualify the public deployment.

Reference

  • MCP reference owns discovery and execution tool syntax.
  • Runs and lineage owns Run status and readback.
  • Agents explains agent work. Its workflow adapter is not an MCP Surface.