Alchemist Cloud Tickets MCP
Dispatch and track Alchemist Cloud tickets, watch deploys, read logs, and query your project DB.
ai.chipp · 21 listed services · provider site
Dispatch and track Alchemist Cloud tickets, watch deploys, read logs, and query your project DB.
Every Chipp tool in one MCP (large). For one area at a time, use the ai.chipp/chipp-* servers.
Chipp: custom actions, action collections, custom components, and database connections
Chipp: conversations, messages, usage and engagement analytics, end users and their memories, and.
Chipp: the full agent settings writers (update_app, bulk_update_app_settings), branding, auth.
Chipp: create, publish, version, chat with and move agents; system prompt, model, suggestions.
Chipp: the subscription, credits, usage and capabilities, and consumer packages an agent sells
Chipp: Slack, email, WhatsApp, GitHub, Discord and voice deployments, and heartbeat schedules
Chipp: who you are, workspaces, finding agents, Chipp docs, and the list of the other Chipp MCPs
Chipp: changes to a deployed project's live data: data, script and procedure operations, bulk.
Chipp: hosted integrations and their catalog, and MCP servers connected to an agent
Chipp: knowledge sources (URLs, sitemaps, text, documents), crawls, and evidence search over an.
Chipp: the code of an app being rebuilt: the imported GitHub repo and the legacy codebase
Chipp: a project's memory, circles, and scheduled tasks
Chipp: newsletter topics, audiences, contacts, campaigns and sends
Chipp: a deployed project's database (read), logs, errors, analytics, CI status, custom actions.
Chipp: the feature pack and recipe catalog, pack installs, checkout, and the project blueprint
Chipp: software factory projects: list, create and scope them, and the factory tools in no other.
Chipp: software factory deploys and releases: history, the deploy gate, Deploy now, rollbacks.
Chipp: conversation tags, their training examples and utterances, and tag instances
Chipp: software factory tickets: list, read, file, reply, retry, cancel, proposals, and child.
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.