Caspio

com.caspioPublished by caspio.comOfficial publisherv1.2.2Updated Oct 25, 2026

Your Caspio data is MCP-enabled. Bring any dataset and put your AI assistants to work. No coding.

VerifiedStreamable HTTPWeb executableDatabasesData & Analytics

Overview

AI-generated overview

Caspio's remote MCP server connects AI assistants to your Caspio data so they can work with your datasets without coding.

What you can do
Connect an assistant to your Caspio data through an MCP-enabled endpoint, so it can work with the datasets you bring to Caspio. The manifest lists no individual tools, so the exact operations available are not documented here. The provider positions it as a no-code way to put AI assistants to work on your data.
When to use it
Useful if you already keep data in Caspio and want an AI assistant to work with it directly, without building custom code or integrations.
Requirements
A remote MCP endpoint at mcp.caspio.com, reached over streamable HTTP. OAuth authentication is required, so you need a Caspio account and must authorize the connection. No environment variables or headers are declared.
Before you install
The connection is authorized through OAuth and gives the assistant access to your Caspio data; review which account and permissions you grant. The manifest does not list the tools, so confirm whether the assistant can only read data or can also create, change, or delete records before connecting.

Installation

In SourceWeft

  1. Open Caspio in the dashboard and add it to a workspace.
  2. Connect the required 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/com.caspio%2Fcaspio/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "caspio": {
      "type": "http",
      "url": "https://mcp.caspio.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.2LatestSep 21, 2026
  2. v1.2.0Sep 18, 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.