Sinatra

dev.sinatraPublished by sinatra.devOfficial publisherv1.0.1Updated Oct 24, 2026

Hosted coding agent: start, follow up on and stop tasks that can open GitHub pull requests.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A hosted coding agent that lets an assistant start, follow up on, and stop tasks which can open GitHub pull requests.

What you can do
Sinatra is a remote MCP endpoint for a hosted coding agent. Through it, an assistant can start coding tasks, send follow-up instructions to a running task, and stop tasks. Tasks can open GitHub pull requests, so the agent's work can land as reviewable changes.
When to use it
Useful when you want an assistant to hand coding work to a hosted agent and track it, rather than editing code directly. Suited to workflows where results should arrive as GitHub pull requests for review.
Requirements
Runs as a remote endpoint at api.sinatra.dev over streamable HTTP. Authentication is OAuth and is required. No packages, environment variables, or headers are declared.
Before you install
OAuth grants the server access on your behalf, and tasks can open GitHub pull requests, which writes to your repositories. Review what the agent changes before merging, and check which repositories and permissions the OAuth grant covers.

Installation

In SourceWeft

  1. Open Sinatra in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/dev.sinatra%2Fsinatra/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sinatra": {
      "type": "http",
      "url": "https://api.sinatra.dev/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 16, 2026
  2. v1.0.0Oct 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.