Chipp Data operations

ai.chippPublished by chipp.aiOfficial publisherv1.0.0Updated Oct 29, 2026

Chipp: changes to a deployed project's live data: data, script and procedure operations, bulk.

The publisher's own server: Alchemist Cloud Tickets

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote Chipp MCP endpoint for making changes to a deployed project's live data, including data, script and procedure operations and bulk changes.

What you can do
  • Apply changes to the live data of a deployed Chipp project
  • Run data, script and procedure operations against that project
  • Perform bulk operations rather than one change at a time
  • No individual tools are listed in the manifest, so the exact commands are not documented here.
When to use it
Useful when an assistant needs to modify the live data of a Chipp project that is already deployed, including bulk updates, rather than only read it.
Requirements
A remote streamable HTTP endpoint at mcp.chipp.ai; no packages, environment variables or headers are declared. The manifest declares no authentication, so access control is unclear from the supplied information.
Before you install
It operates on live data of a deployed project, so operations can change or delete production data, and bulk operations can affect many records at once. No authentication is declared, so confirm how access is restricted before connecting.

Installation

In SourceWeft

  1. Open Chipp Data operations in the dashboard and add it to a workspace.
  2. 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.chipp%2Fchipp-data-ops/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": {
    "chipp-data-operations": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/data-ops"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

Other Chipp integrations