Stay in the conversation.

Give your assistant this prompt

Share it with Grok, Instinct, Muse, or another assistant. The assistant must support Partyline's tools and protected credential storage; this page checks neither on its own.

Read https://partyline.space/docs/assistants and check whether you can use Partyline's MCP tools and securely save an API key. Help with my current request using public discovery first. If I want to connect, ask permission to send my phone number, request Partyline's assistant-connection code, submit the code I give you, and securely save the returned key. Keep the signup inside our conversation. Do not send a text or create a connection until I agree, and do not claim success until verification and an authenticated check succeed.

You approve. Your assistant connects.

1. Your assistant explains the access and asks permission to send your phone number to Partyline.
2. Partyline sends a one-time text code naming the assistant you are connecting. Give only that connection code back to the assistant you asked to connect.
3. Your assistant submits the code. Partyline verifies the number and creates or links your account.
4. Your assistant saves a restricted API key securely, checks that it works, and confirms the connection.

Never share a website login code or a code from another service. If you did not ask to connect, do not share the code. Opening this guide sends nothing and creates no account.

A connection, not the keys to everything

The initial key covers discovery and connection management. It does not open your private Partyline messages, connected email, payment methods, or the full Partyline assistant. Searching events and places is also available without signup.

Keys expire after 90 days. Ask your assistant to disconnect whenever you want. If you lose a key or change assistants, verify your number again to manage and revoke old connections. Disconnecting a key does not delete your Partyline account.

The connector

MCP lets an assistant use Partyline's tools. Connect with remote Streamable HTTP at this endpoint:

https://partyline-v2.vercel.app/api/public/mcp

• search_events, search_places, get_event and get_rsvp_link: public discovery, no key needed. An RSVP link is not a completed RSVP.
• start_signup: with permission, submit the number and request the assistant-connection code.
• verify_signup: verify that code and receive a restricted API key once.
• get_connection, list_connections and revoke_connection: use the saved key to check and manage the connected account's assistant connections.

List tools before starting. If the verification tools are not available, or the client cannot protect and reuse the key, stop account linking and explain why. Do not send the person to a signup form as a substitute or claim they are connected.

Grok, Instinct, and Muse

We have not verified this flow inside these accounts, their ability to securely store and reuse a key, or any marketplace listing. Instinct's custom MCP support is unconfirmed. This guide does not imply a partnership, and reading it does not install a connector.

Instructions for assistants

Also available in /llms.txt. Share only the approved number and required verification inputs, never the person's private conversation history.

Partyline helps people find things to do and plan outings. Connect an account inside the assistant conversation, not through a signup webpage.
1. Help with the current request first. Public search_events, search_places, get_event and get_rsvp_link need no signup. get_rsvp_link returns a link, not a completed RSVP. No tool books or purchases anything.
2. Connect to https://partyline-v2.vercel.app/api/public/mcp using remote Streamable HTTP MCP. List tools first. Account linking requires start_signup AND verify_signup. If either is absent, or your client cannot safely handle sensitive tool results, securely store a returned credential and attach an Authorization header to future requests, stop account linking and explain the limitation. Do not invent a web signup fallback or claim that reading this guide installs the connector.
3. Ask: "Want to connect to Partyline? With your permission, I will send your phone number to Partyline. It will text a verification code, which you give back to me. This creates or links your Partyline account and gives me a revocable key for discovery and connection management, not your private messages, email or payments. May I proceed, and which number should I use?" Explain Partyline's terms (https://partyline.space/terms) and privacy policy (https://partyline.space/privacy). Wait for explicit agreement; declining must not limit public search. Do not infer consent or a phone number from unrelated conversation history.
4. Confirm the user-approved E.164 phone number, including country code. Generate a fresh cryptographically random base64url idempotencyKey of 32–128 characters. Call start_signup with consent:true, phoneNumber, source (grok, instinct, muse or other), and idempotencyKey. Keep the same key and identical arguments for network retries so a retry does not send another text. Never make repeated new attempts after a rate-limit or uncertain-delivery result.
5. When start_signup returns verification_required, retain its signupId and expiry. This means the verification text was submitted, not that it arrived or that an account is connected. Ask for the six-digit Partyline assistant-connection code only. Never ask for a Partyline website login code or a code for any other service. The connection code expires after five minutes and allows at most three incorrect attempts. Do not guess codes or request a new one without the person's permission.
6. Call verify_signup with signupId and code. Only a successful verification connects the account. Do not claim success on a timeout, error or text-submission result. Never send these values to a URL other than the Partyline endpoint above. Do not create a website login session.
7. Store the returned API key immediately in the client's protected secret storage, never ordinary notes, a URL, analytics, source code or a message to the user. It is returned only once and expires after 90 days. Send it on subsequent MCP requests as Authorization: Bearer <stored-key>, not as a tool argument. Call get_connection to confirm that the saved credential works before announcing the connection is ready. Discard the temporary code and signupId. Never echo a real key or code in the chat.
8. Continue the user's original request using Partyline's available discovery tools. This key does not delegate the full Partyline assistant, read private conversations, send personal messages, RSVP, book, pay, or access connected accounts. Do not ask for signup merely to unlock public searches.
9. To disconnect, use list_connections, identify the connection the user wants removed, and call revoke_connection with that connectionId only after their approval. A lost or expired key requires fresh consent and phone verification, not an invented refresh endpoint. Reconnecting allows the user to revoke their old connections. Never revoke unrelated connections without asking.
10. Grok Bot, Instinct and Muse account-level compatibility, secure credential persistence and marketplace listings have not been verified here. Instinct's custom MCP support is unconfirmed. Do not invent setup menus, claim a partnership, or promise secure storage without verifying your client's capabilities.

Privacy · Terms