Chipp Agent settings

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

Chipp: the full agent settings writers (update_app, bulk_update_app_settings), branding, auth.

The publisher's own server: Alchemist Cloud Tickets

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote Chipp MCP endpoint that lets an assistant write agent settings, including bulk settings updates, branding and auth configuration.

What you can do
  • Update an app's agent settings, including bulk changes across many settings at once.
  • Adjust branding and authentication configuration for the app.
  • The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to change Chipp agent configuration directly, especially batch edits to settings, branding or auth, instead of editing them by hand in the Chipp interface.
Requirements
A remote streamable HTTP endpoint at mcp.chipp.ai; no packages, environment variables or headers are declared. The manifest declares no authentication, though the description mentions auth settings, so check what credentials the endpoint expects.
Before you install
The tools write configuration: update_app and bulk_update_app_settings can change or overwrite agent settings, branding and auth in bulk, so review changes before running them. No authentication is declared in the manifest, so confirm how access to the endpoint is controlled.

Installation

In SourceWeft

  1. Open Chipp Agent settings 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-app-settings/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-agent-settings": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/app-settings"
    }
  }
}

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