Chipp Integrations

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

Chipp: hosted integrations and their catalog, and MCP servers connected to an agent

The publisher's own server: Alchemist Cloud Tickets

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Server details

Identifier: ai.chipp/chipp-integrations
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 29, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to chipp.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.chipp%2Fchipp-integrations.svg)](https://sourceweft.com/mcp/ai.chipp%2Fchipp-integrations?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Chipp Integrations is a hosted Chipp endpoint that exposes the integration catalog and the MCP servers connected to an agent.

What you can do: The input lists no tools, so capabilities are inferred from the short description.
It is described as a hosted service covering Chipp integrations and their catalog.
It also covers MCP servers connected to an agent, suggesting an assistant can reach those connected servers through this endpoint.
No tool names, parameters or usage details are documented in the supplied material.
When to use it: Consider it if you already work inside Chipp and want an assistant to see which integrations exist and reach the MCP servers attached to an agent, rather than adding each server separately.
Requirements: A remote streamable HTTP endpoint at mcp.chipp.ai; no packages, environment variables or headers are declared. The manifest declares no authentication, but a Chipp account or agent context is likely needed to use it.

Before you install

The manifest declares no authentication and no credentials, yet the endpoint is described as exposing an agent's connected MCP servers, so check how access is controlled before connecting. No tool list is published, so what it can read or change is unknown.

Installation

In SourceWeft

Open Chipp Integrations in the dashboard and add it to a workspace.
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-integrations/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-integrations": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/integrations"
    }
  }
}

Tools

SourceWeft has not read this server's tools yet.

Version history

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.

Not indexed yetOct 29, 2026