Integration

Geneea integration

Geneea's General API (G3) analyzes text in English, Czech, German, Spanish, French, Dutch, Polish and Slovak. One call detects the language, finds named and general entities (people, organizations, locations, products) linked to the Geneea knowledge base, assigns semantic tags with relevance, extracts relations such as cancel(John, subscription), and scores sentiment for the whole document and, on request, for each entity and sentence; domains tune it to news and media or to customer feedback. You can also read the account's plan, quotas and billing period. The POST, batch and per-analysis shortcut routes, document-file analysis and custom tasks are not included: the text travels in the query string. Authentication is a Geneea API key sent in the Authorization header with the user_key prefix.

Connect Geneea How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Geneea.Built from the 2 Geneea tools below, on the connection you add once.

What you can do with Geneea

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Account, 1 operation

get_accountGet accountGETReturns the plan of the Geneea account behind the API key, the quotas used and remaining, and the current billing period with its start and end. Called without a key, it answers with the ANONYMOUS type and empty quotas.

Text, 1 operation

analyze_textAnalyze textGETAnalyzes a text in one call: language, named and general entities linked to the Geneea knowledge base, semantic tags with relevance, relations and document sentiment, as chosen in analyses (all by default).

Use Geneea from Claude Code, Cursor or Codex

Connect Geneea in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Geneea operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Geneea

Create your workspace
Sign up free. Nothing to install.
Connect Geneea once
Add your Geneea connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.