---
title: "Hamster OSS MCP server"
description: "Connect Claude, ChatGPT, Cursor or any MCP client to your team's Hamster OSS instance at https://<your-team>.tryhamster.dev/mcp over Streamable HTTP with OAuth."
canonical: "https://tryhamster.dev/docs/mcp"
last-updated: "2026-11-05"
---

# Hamster OSS MCP server

> Connect Claude, ChatGPT, Cursor or any MCP client to your team's Hamster OSS instance at https://<your-team>.tryhamster.dev/mcp over Streamable HTTP with OAuth.

*Every Hamster OSS instance runs an MCP server at `https://<your-team>.tryhamster.dev/mcp`. Your agent works inside one project, with the permissions of the team member who approved the connection.*

`https://tryhamster.dev/mcp` is a separate server: the Hamster OSS account MCP server. Without sign-in it answers `get_pricing`, `search_docs`, `fetch_doc` and `get_install_command`. After the person approves your agent through OAuth with tryhamster.dev, it can also create an instance for them, report its status, redeem a Design Partner Code, and send them to a Stripe-hosted page that either saves and verifies a card for $15 in starter credit without a payment, or adds funds and saves their card for later top-ups. It holds no team data; for that, connect to the instance. [Hamster OSS API](https://tryhamster.dev/developers) lists its tools and scopes.

## Endpoint

- URL — `https://<your-team>.tryhamster.dev/mcp`
- Transport — Streamable HTTP. Requests are JSON-RPC 2.0 over `POST`, and the server answers with JSON. It keeps no server sessions, so every request authenticates again.
- Protocol revisions — 2024-11-05 through 2026-07-28.
- Authorization — OAuth with the `system:access` scope, or an expiring token from **Connect your agent**.

## Tools

The server has six tools. Each takes a `path` that names a thing, the way a REST URL does:

- `read` — read one thing or list a collection. Start with `read /`.
- `search` — find knowledge by words or by a feature request.
- `create` — start something new, such as an ask for the Discovery agent.
- `update` — change something that exists, such as an answer.
- `delete` — remove or end something.
- `message` — send a message to an agent conversation.

Every call runs as the team member who granted access, and Studio checks that grant on each call. Every tool is idempotent: a change is keyed by the `?key=` in its path or by its content, so repeating a call after a timeout has no further effect.

## Sign-in and discovery

Clients that support MCP authorization need only the URL. The first request without a token gets `401` and a `WWW-Authenticate` header that points to `/.well-known/oauth-protected-resource/mcp`. That document names the instance as the authorization server and lists the `system:access` scope. The client reads `/.well-known/oauth-authorization-server`, registers through `/oauth/register` and opens `/oauth/authorize` with S256 PKCE. You sign in to your instance and choose the project.

## Client setup

Claude Code:

```sh
claude mcp add --transport http hamster https://<your-team>.tryhamster.dev/mcp
```

A project `.mcp.json`:

```json
{
  "mcpServers": {
    "hamster": {
      "type": "http",
      "url": "https://<your-team>.tryhamster.dev/mcp"
    }
  }
}
```

In ChatGPT or Claude on the web, add a custom connector with the same URL.

## Tokens without OAuth

For a client that can't run OAuth, open **Connect your agent** in Studio, or **Agents** in your settings, and create a token for one project. Tokens expire. Revoking a connection stops further access, and reconnecting replaces the grant. Send the token as `Authorization: Bearer <token>`.

[Hamster OSS API](https://tryhamster.dev/developers) has example requests, and the [OpenAPI document](https://tryhamster.dev/openapi.json) has the request and response schemas.