Agents Index

Algenta MCP Server

Online

Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.

Visit publisherConnectJSON

What it can do: 80 tools

  • onboard_datasetRegister a dataset for semantic querying. Pass column names, inline records, or raw CSV. The engine profiles roles automatically and starts background training. Queries work immediately via a fallback model — accuracy im
  • list_datasets read-onlyList registered datasets and their current model tier. Use search plus compact mode for low-token discovery, then poll status or use the primary data tools once you choose a dataset. Read-only and non-destructive; lists
  • get_dataset_status read-onlyGet the live training status and model tier of one dataset: whether semantic training is still running or the dataset is ready, and which model serves queries — model_tier 'none' = deterministic fallback only, 'base' = g
  • retrain_datasetRe-trigger background semantic training for one dataset and return immediately with status and a confirmation message — the build runs asynchronously, so poll get_dataset_status until model_tier reaches 'schema'. Use aft
  • connect_dataHigh-level data onboarding flow. Use this instead of advanced connector/source tools for normal users. Connect data once, pick the table/file/endpoint, and get a reusable dataset_id. If the result status is needs_selecti
  • list_data read-onlyList visible datasets for the current user. Use search plus compact mode first for low-token dataset discovery, then get_data_schema on the chosen dataset_id. Read-only and non-destructive; lists only the active API key'
  • get_data_summary read-onlyGet the low-token dataset selection summary for a saved dataset_id. Use this after list_data(search=..., compact=true) before paying for the full schema payload. Read-only and non-destructive; reads only the active API k
  • get_data_schema read-onlyGet a saved dataset plus its schema and relationship metadata by dataset_id. Read-only and non-destructive; reads only the active API key's organization and is not separately rate-limited. Use get_data_summary first for
  • refresh_dataRe-pull a saved dataset from its original database, API, or object-store origin using the stored connection and selection, and return the same envelope as connect_data (status, schema_summary, refreshable). Only datasets
  • disconnect_dataDelete a saved dataset and disconnect it from future use. When no other dataset in the workspace still uses the backing saved connection, that connection is deleted too and connection_deleted is true in the response. Req
  • register_sourceAdvanced tool. Register a data source and get full schema profiling + join detection. Profiles every column (type, cardinality, fill rate, distribution). Detects formula relationships (A×B≈C) within the source. Detects j
  • list_sources read-onlyAdvanced tool. List all registered data sources for this org with their schema summaries. Use this to discover available tables before calling query_data or register_source. Read-only and non-destructive; not separately
  • get_source_schema read-onlyAdvanced tool. Get the full schema for a specific registered source: column types, cardinality, fill rates, formula relationships, and detected join keys to other sources. Read-only and non-destructive; not separately ra
  • list_connectors read-onlyList the data connectors saved under the caller's organization — databases, APIs, file-backed, and repository sources — with id, name, connector_type, status (untested, live, error), and visibility; stored credentials ar
  • create_connectorSave one connector configuration (host, credentials, options) for later data onboarding, health checks, and schema browsing. config is encrypted at rest and the new connector starts untested — call test_connector to veri
  • get_connector read-onlyFetch one saved connector by connector_id: name, connector_type, status, visibility, timestamps, and the config fingerprint — never the stored credentials. Use list_connectors to find ids. Read-only; an unknown or invisi
  • update_connectorPartially update one saved connector: only the supplied fields change. Passing a new config replaces the encrypted credentials and resets the connector to untested, so call test_connector again afterwards. Requires manag
  • test_connectorRun a real connectivity test against one saved connector's stored config and persist the outcome as its live or error status with last_tested_at. This opens an actual connection to the source. Use preview_test_connector
  • browse_connector read-onlyDiscover what one saved connector exposes — files, tables, endpoints, or items — with discovery labels and metadata for choosing what to onboard. The connector must be live: an untested or errored connector fails with no
  • preview_test_connector read-onlyRun a real connectivity test against an inline connector definition without saving anything — the dry run for create_connector. This opens an actual connection to the source, is rate-limited per organization, and caches
  • preview_browse_connector read-onlyBrowse one inline connector definition without saving it to discover files, tables, endpoints, or items. This opens a real connection to the source and is rate-limited per organization; nothing is saved. Use browse_conne
  • delete_connectorDelete one saved connector by id. Use update_connector to change config without losing the saved definition. Deleting is idempotent: repeating the call on an already-deleted or never-existing id returns success with alre
  • get_repository_intelligence_capabilities read-onlyList globally supported Repository Intelligence languages and ranked support progress. Read-only and non-destructive. Check language support here before create_repository_snapshot. Returns supported_languages and support
  • create_repository_snapshotCreate or reuse an immutable, content-hashed snapshot of a saved repository connector (a connector of a repository type — find its id with list_connectors). Re-running with identical inputs returns the existing snapshot
  • get_repository_snapshot read-onlyFetch one persisted immutable repository snapshot by repository_id and snapshot_id, including its resolved_revision, content_hash, file_count, language_counts, and graph artifact refs. Use this to re-read a snapshot crea
  • triage_repositoryCondense one repository snapshot into a bounded workspace evidence bundle for the planner: ranked suspect files and symbols with scored, budget-capped snippets. signals seeds the search — pass issue_text, diagnostics, fa
  • create_repository_decision_planCreate one stored, immutable repository DecisionPlan revision from a triage workspace evidence bundle and return its decision_plan_id plus the validated patch diff inline. snapshot_id is resolved from the bundle when omi
  • query_repository_graphWalk the dependency graph of one persisted repository snapshot from optional file_path/symbol_name seeds and return impacted files and symbols with change-risk scores. Seed scope comes from snapshot_id or a triage worksp
  • simulate_repositoryScore the patch risk of a stored repository DecisionPlan with the deterministic simulation engine and return the gated DecisionEnvelope whose apply gate apply_repository checks. snapshot_id is resolved from the plan when
  • run_repository_pipelineRun the whole repository-intelligence chain — snapshot, triage, plan, simulate — in one call and return the canonical repository envelope with every stage's response, stage timings, and the ids (snapshot_id, plan_id, sim
  • simulate_repository_patchSimulate the risk of an in-flight unified diff against one persisted snapshot and return the canonical repository envelope — without creating a stored decision plan. Use this to verify a working-tree patch mid-run; use s
  • run_repository_fixRun the repository pipeline and then apply its result in one call, returning the canonical repository envelope for both stages. pipeline takes run_repository_pipeline's arguments and must complete through simulate (the c
  • apply_repositoryMaterialize a simulated repository decision in one of three modes. patch_only just returns the validated patch diff with applied=false and writes nothing. local_branch commits the patch to a new branch (default algenta/<
  • query_data read-onlyExecute a structured query against connected data sources. Convert the user's question to a structured intent and call this tool — do NOT try to write SQL or parse column names yourself. The engine resolves column meanin
  • query_batch read-onlyExecute several governed exact queries in one API call. Use this for multi-metric prompts after choosing a dataset with list_data and get_data_summary. Each item reuses the same structured query contract as query_data; d
  • query_sql_report read-onlyExecute a constrained read-only SQL rowset query over authorized datasets. Use this only for wide reports that do not fit the governed exact-query surface. SQL must be a single SELECT/WITH statement over the provided dat
  • ingest_data read-onlyAuto-map tabular data to a simulation payload. Detects variable distributions, polarity (revenue=positive, cost=negative), units, and builds the objective function automatically. Set run_simulation=true to execute the si
  • list_models read-onlyList the current Algenta model catalog, including deterministic utility models and any provider-backed routed entries with their routing, failover, timeout, and auth metadata, including capability-specific chat and embed
  • resolve_artifact_bridgeResolve a Hugging Face artifact path through the Algenta compatibility-ring artifact bridge. Defaults to cache-only lookup and never downloads unless local_files_only=false. Use this only for Hugging Face artifact paths;
  • tokenize read-onlyTokenize UTF-8 text into individual tokens with a supported deterministic Algenta tokenizer model (default text.tokenizer; call list_models for every supported model id). Use this when you need the token strings themselv

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http algenta-mcp-server https://api.algenta.ai/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.algenta.ai/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "algenta-mcp-server": {
      "url": "https://api.algenta.ai/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "algenta-mcp-server": {
      "type": "http",
      "url": "https://api.algenta.ai/mcp"
    }
  }
}

Questions

What does Algenta MCP Server do?

Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP. It exposes 80 tools to AI assistants.

What tools does Algenta MCP Server provide?

80 tools, including onboard_dataset, list_datasets, get_dataset_status, retrain_dataset, connect_data, list_data, get_data_summary, get_data_schema, refresh_data, disconnect_data, register_source, list_sources….

How do I connect Algenta MCP Server to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.algenta.ai/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Algenta MCP Server require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Algenta MCP Server online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Algenta MCP Server?

@thyn-ai on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Developer Tools