> For the complete documentation index, see [llms.txt](https://docs.algenta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algenta.ai/mcp-tools.md).

# MCP tools

- [MCP tools overview](https://docs.algenta.ai/mcp-tools/overview.md): The Algenta MCP server exposes the engine as Model Context Protocol tools for Cursor, Claude, and other hosts. Browse the tool catalog by domain.
- [Data & ingest tools](https://docs.algenta.ai/mcp-tools/data.md): MCP reference for Algenta data tools — onboard and train datasets, run the high-level connection flow, register sources, and ingest tables to a simulation.
- [Connector tools](https://docs.algenta.ai/mcp-tools/connectors.md): MCP reference for Algenta connector tools — create, inspect, test, browse, update, and delete saved data connectors, plus preview inline definitions.
- [Query tools](https://docs.algenta.ai/mcp-tools/query.md): MCP reference for Algenta query tools — governed exact queries, multi-metric batches, and constrained read-only SQL reports over your authorized datasets.
- [Repository intelligence tools](https://docs.algenta.ai/mcp-tools/repository-intelligence.md): MCP reference for Algenta's repository-intelligence tools — snapshot, triage, plan, graph-query, simulate, and apply a code fix from any MCP client.
- [LLM utility tools](https://docs.algenta.ai/mcp-tools/llm.md): MCP reference for Algenta's deterministic utility-model tools — list models, tokenize, count tokens, chat, responses, embeddings, similarity, and rerank.
- [Capability plane tools](https://docs.algenta.ai/mcp-tools/capability-plane.md): MCP reference for Algenta's capability plane — list providers and bindings, discover and test them, route an objective, execute a capability, and manage skills.
- [Decision tools](https://docs.algenta.ai/mcp-tools/decisions.md): MCP reference for Algenta's decision tools — simulate, recommend, score, compare, the product helpers, and the decision-memory log/outcome loop.
- [Async jobs & triggers tools](https://docs.algenta.ai/mcp-tools/jobs-and-triggers.md): MCP reference for async simulation jobs and real-time triggers — submit and poll long-running jobs, test webhooks, and register conditions that auto-run simulations.
- [Agent run tools](https://docs.algenta.ai/mcp-tools/agent-runs.md): MCP reference for the Algenta agent-run lifecycle — create runs, read events, checkpoints, mission events and telemetry, and resume, cancel, or approve a run.
- [Control plane tools](https://docs.algenta.ai/mcp-tools/control-plane.md): MCP reference for deployments, team members, devices, audit logs, execution policy, billing, and managed-runtime compatibility.
- [Account & meta tools](https://docs.algenta.ai/mcp-tools/account-and-meta.md): MCP reference for account, identity, API keys, usage and runtime discovery — the get\_contract, get\_me, key-management, run-history and analytics tools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.algenta.ai/mcp-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.