Chipp
ai.chippPublished by chipp.aiOfficial publisherv1.1.0Updated Oct 29, 2026
Every Chipp tool in one MCP (large). For one area at a time, use the ai.chipp/chipp-* servers.
The publisher's own server: Alchemist Cloud Tickets
Overview
Chipp's combined remote MCP server that exposes all Chipp tools in one connection, with OAuth sign-in.
- What you can do
- No tool list is published, so capabilities can only be inferred from the description.
- It bundles every Chipp tool into a single MCP connection rather than splitting them by area.
- The provider also offers separate area-specific Chipp servers for narrower use.
- When to use it
- Consider it when you want one connection covering all Chipp functionality instead of adding several area-specific Chipp servers. For focused work in a single area, the provider's narrower servers are suggested instead.
- Requirements
- A remote streamable HTTP endpoint at build.chipp.ai; no local package or runtime is needed. OAuth authentication is required, so a Chipp account and a client that supports OAuth are needed. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Chipp in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"chipp": {
"type": "http",
"url": "https://build.chipp.ai/mcp"
}
}
}Tools
0Version history
2- v1.1.0LatestOct 29, 2026
- v1.0.0Sep 16, 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.
Other Chipp integrations
Alchemist Cloud Tickets
ai.chippOfficial publisher
Lets an assistant dispatch and track Alchemist Cloud tickets, watch deployments, read logs, and query a project database.
Chipp Tickets
ai.chippOfficial publisher
Chipp Tickets's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Tags
ai.chippOfficial publisher
Chipp Tags's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Releases
ai.chippOfficial publisher
Chipp Releases's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.
Chipp Software factory projects
ai.chippOfficial publisher
Chipp Software factory projects's hosted MCP server, published by chipp.ai; no sign-in required; Streamable HTTP.