Cobbles

ai.cobblesPublished by cobbles.aiOfficial publisherv1.0.0Updated Oct 24, 2026

The shared task board for teams and their AI agents — connect over OAuth, every action signed.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Cobbles is a remote MCP endpoint for a shared task board where teams and their AI agents coordinate work, with OAuth sign-in and signed actions.

What you can do
  • Connect an assistant to a shared task board used by teams and their AI agents.
  • Coordinate work items on that board through the remote endpoint, with each action attributed and signed.
  • Sign in through OAuth rather than pasting a static key.
  • The registry lists no individual tools, so the exact operations available are not documented here.
When to use it
Consider it when a team wants its AI agents to work from the same task board as the people, and needs actions traceable to a signed identity. It is less useful if you only need a personal to-do list or a board that is not shared with agents.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. An OAuth sign-in with the service is implied by the description; no environment variables or headers are declared.
Before you install
The description says every action is signed, so activity on the board is attributable to the connected identity; review what the assistant is allowed to change on shared team tasks. No tool list is published, so confirm the scope of write access before connecting. The manifest declares no authentication details, so verify the OAuth flow during setup.

Installation

In SourceWeft

  1. Open Cobbles 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.cobbles%2Fcobbles/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": {
    "cobbles": {
      "type": "http",
      "url": "https://api.cobbles.ai/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.