OpenAna + Model Context Protocol (MCP)

Ana SDE is an MCP client: connect any MCP server and Ana can use its tools and read its resources, with your approval on every call.

Open protocolIDE

Ana + Model Context Protocol (MCP)

What Ana does with it.

Ana SDE runs inside your editor - chat, plan and let the agent build, with your approval at each step.

  • 01

    Plug internal APIs, databases, docs and SaaS tools into Ana through MCP servers

  • 02

    Ana calls MCP tools and reads MCP resources as part of its plan

  • 03

    Every MCP call is shown and runs one at a time, only after you approve it

  • 04

    Server config lives in a settings file and reloads live when you edit it

Setup

Connected in four steps.

  1. 1

    Pick a server

    Use an existing MCP server for your tool, or wrap an internal API in one.

  2. 2

    Add it to Ana

    Declare it under mcpServers in Ana SDE’s MCP settings - command, args and env. Edits reload live.

  3. 3

    Ana discovers it

    Ana lists the server’s tools and resources and can plan with them.

  4. 4

    Approve each call

    Every MCP tool call or resource read is shown first and runs one at a time with your approval.

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with Model Context Protocol (MCP), route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.

FAQ

OpenAna and Model Context Protocol (MCP).

Any MCP server that runs locally over standard input/output (stdio) - community servers for popular tools, or your own server wrapping an internal API, database or knowledge base.

See it connected

Ana on your Model Context Protocol (MCP).

Thirty minutes, your real setup, one real problem.