# Tim MCP Server - Briefs for AI Agents > Connect Claude, ChatGPT or your own AI agent to Tim over MCP: ask about Timerise, then create and submit a project brief for yourself or for your customers. Page: https://timerise.ai/help/development/tim-mcp-server Tim, the Timerise assistant, is also an MCP server. Any AI agent can ask Tim about Timerise, and a signed-in agent can create a project brief and send it to the Timerise team, the same brief a person fills in at [/brief](/brief). This is not the booking API's MCP server. For bookings, services and slots, see [MCP Server - AI Agent Integration](/help/development/mcp-server-ai-agent-integration). ## Server URL ``` https://timerise.ai/api/mcp ``` Streamable HTTP. Asking questions needs no sign-in; the brief tools do, and a guest sign-in with no email is enough to draft. An agent that has not connected yet can find the server on its own: the server card is at `/.well-known/mcp/server-card.json` (also `/.well-known/mcp.json`), [llms.txt](https://timerise.ai/llms.txt) has an "MCP server" section, and opening the server URL in a browser returns the same card. `https://timerise.ai/mcp` redirects to the server URL. ## Tools | Tool | Sign-in | What it does | | ---------------- | ------- | ------------------------------------------------------------------------------------------------ | | `ask_tim` | No | Ask Tim anything about Timerise. Pass the returned `sessionId` on follow-ups. | | `search` | No | Search the help center, blog, manifesto and case studies. | | `fetch` | No | Read one document found by `search`. | | `request_access` | No | Email a 6-digit code, for agents that cannot use OAuth. | | `verify_access` | No | Trade the code for an API key, shown once. For a guest, link the email instead. | | `guest_access` | No | Get a guest API key at once, with no email. | | `whoami` | Yes | Who the connection acts as. | | `create_brief` | Yes | Start a draft from free-text `notes` (Timerise drafts the whole brief) and/or structured fields. | | `update_brief` | Yes | Change a draft. | | `get_brief` | Yes | Read a brief, with `readyToSubmit` and what is still missing. | | `list_briefs` | Yes | List your briefs, or the briefs your agent started. | | `submit_brief` | Yes | Send a complete brief to Timerise. It can no longer be changed. | A brief can be submitted once it has the project requirements, a price estimate (USD 15,000 to 50,000, with a breakdown that adds up to the total) and a timeline. Timerise replies to the customer within 48 hours with a clickable prototype and a quote. ## As me, or as an agent When you sign in, you choose who the agent acts as: - **As me:** the agent works on your own brief, filed under your email. You see it at [/brief](/brief) when you sign in. - **As an agent for my customers:** the agent creates briefs for other people's emails under its own name, passing `customerEmail` to `create_brief`. It only sees the briefs it started, and cannot take over a draft someone else began. The Timerise team sees the agent's name on every brief it sends. Either way, one person proves their email once. After that the agent works on its own. ## As a guest You can also connect with no email at all. On the sign-in page choose **Continue as guest**; a script calls `guest_access` and gets an API key at once. A guest can do everything except send: `create_brief`, `update_brief`, `get_brief` and `list_briefs` work on the guest's own draft, and `submit_brief` is refused, because Timerise replies to the customer by email. To send the brief, link an email on the same connection: call `request_access` with the email and `kind` `customer`, then `verify_access` with the code. Nothing is lost: the connection keeps working without signing in again, and the draft moves to your email. If that email already had a draft, that one is kept and the guest draft is returned in the answer so the agent can carry its content over. ## Claude In Claude (web, desktop or mobile), open **Settings > Connectors > Add custom connector**, paste `https://timerise.ai/api/mcp`, and save. Claude asks you to sign in the first time you use a brief tool: you sign in with your email on timerise.ai, choose **As me** or **As an agent**, and are sent back. ## ChatGPT In ChatGPT, turn on **Developer mode**, then create a connector with the URL `https://timerise.ai/api/mcp` and **OAuth** authentication. The sign-in works the same way as in Claude. `search` and `fetch` also make Timerise available as a source for deep research. ## Claude Code ```bash claude mcp add --transport http tim https://timerise.ai/api/mcp ``` Then run `/mcp` inside Claude Code and choose **Authenticate** to sign in in your browser. ## Scripts and other agents: API key Agents that cannot open a browser use an API key: 1. Call `request_access` with an email and `kind` (`customer`, or `agent` with an `agentName`). A 6-digit code arrives by email, valid for 10 minutes. To start without an email, call `guest_access` instead and skip step 2. 2. Call `verify_access` with the email and the code. The response holds the API key, shown only once. 3. Send `Authorization: Bearer ` on every request. ```python from agents.mcp import MCPServerStreamableHttp async with MCPServerStreamableHttp( url="https://timerise.ai/api/mcp", headers={"Authorization": "Bearer tim_your-key-here"}, ) as tim: ... ``` ## Security - OAuth 2.1 with PKCE, discovered through `/.well-known/oauth-protected-resource` and `/.well-known/oauth-authorization-server`, with Dynamic Client Registration and Client ID Metadata Documents. - Tokens are bound to `https://timerise.ai/api/mcp`, access tokens last one hour, and refresh tokens rotate on every use. - Timerise stores only hashes of keys and tokens. To revoke access, write to hello@timerise.ai.