LiveContext

ai.livecontextPublished by livecontext.aiOfficial publisherv1.0.0Updated Nov 4, 2026

Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowAI & ML

Overview

AI-generated overview

LiveContext is a remote MCP server that lets an assistant build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.

What you can do
  • Build and run AI workflows and agents from an MCP client
  • Work with data tables
  • Connect to and use 1000+ API integrations
  • No tool list is published, so exact actions are not documented here
When to use it
Worth adding when you want an assistant to orchestrate multi-step AI workflows, agents and third-party API integrations without leaving the chat client, and you already use or are willing to sign up for LiveContext.
Requirements
A remote MCP endpoint at livecontext.ai over streamable HTTP, with no local package. Requires a LiveContext API key (lc_live_...) sent in the X-API-Key header, created in Settings > MCP Server.
Before you install
The API key is a secret sent in the X-API-Key header; keys can be scoped to a subset of tools, so grant only what is needed. Workflows and integrations may act on external services and change data, and content is processed by LiveContext's remote service.

Installation

In SourceWeft

  1. Open LiveContext in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.livecontext%2Flivecontext/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.