Raq.com for your AI agent
Your agent sets up Raq.com. You just sign in.
Copy one prompt into Claude, ChatGPT Work, Grok Bot or any AI app with connectors. Your agent helps you add Raq.com, then you sign in and choose which accounts it can access. No password to invent.
AI agent reading this page? The same guide is at https://raq.com/agent-start.txt as plain text, without the site navigation.
I want to connect Raq.com to you. Read https://raq.com/agent-start and walk me through it, doing as much as you can yourself. If one way of connecting does not work, try the next one in the guide. Once Raq.com is connected, suggest three useful jobs you could do for my business.
I can set this up now. I will tell you exactly where to add Raq.com in this app, you sign in with your email, and then I will suggest three jobs I can do for your business.
What you do
Your agent handles the technical part. You paste, sign in and approve.
-
Paste the prompt into your AI app.
Claude, ChatGPT Work, Grok Bot or any app with connectors. Your agent reads this guide and takes over.
-
Add Raq.com where your agent tells you.
One screen in your app: a name and an address. Some agents, like Grok Bot, add it themselves.
-
Sign in when Raq.com opens.
Use your email. New here? Create a free account with your name and email. No password needed. If your agent sends you a Raq.com connect link instead, open it and check the code matches.
-
Approve, and you are connected.
Your agent can now use Raq.com tools and suggests three jobs it could do for you.
Where Raq.com goes in your app
Your agent tells you this in the chat. It is here too, in case you want to do it yourself.
https://raq.com/mcp/agent/v1
Claude
Claude web, desktop and mobile share one connector list. Every plan can add custom connectors, and Free allows one.
- Choose Add to Claude to open the Add custom connector dialog with Raq.com filled in. Or open Customize, then Connectors, choose the plus button, then Add custom connector. Name: Raq.com. Server URL: https://raq.com/mcp/agent/v1
- Leave every other setting as it is and choose Add.
- Choose Connect next to Raq.com and approve access when Raq.com opens.
- In a chat or task, turn Raq.com on from the plus menu, then Connectors.
- Team and Enterprise plans: an Owner adds it for everyone with the Owner link, or under Organization settings, Connectors (Add, Custom, Web). Members then open Customize, Connectors and choose Connect next to Raq.com.
ChatGPT and ChatGPT Work
Set up the connection on ChatGPT web. ChatGPT Work uses the same connected apps. Availability depends on your ChatGPT plan and workspace permissions.
- Open chatgpt.com/plugins, select the plus button, then Add custom MCP server. Some accounts show Create MCP App instead. If your workspace uses Apps settings, choose Apps, then Create; Developer mode may be under Advanced settings.
- On Business, Enterprise and Edu, an admin may need to enable custom apps under Workspace settings, Permissions & Roles, Connected Data. Business setup requires an admin or owner.
- Name: Raq.com. Description: Connect your Raq.com workspace and tools. Authentication: OAuth. Leave Client ID and Client Secret empty when offered. Copy this server URL without punctuation: https://raq.com/mcp/agent/v1
- Review the permission notice and choose Create as a plugin (or Scan Tools / Create). Sign in when Raq.com opens, select the accounts you want to connect, approve, and wait for the tool scan to finish.
- Install the resulting plugin if prompted. In a new chat or Work task, type @ and select Raq.com, then ask it to list your available modules.
Grok Bot and Grok
Grok Bot adds the server itself when asked. SuperGrok, Teams and Enterprise plans, and Grok Bot through Cursor.
- In Grok Bot, ask it to add a custom MCP server called Raq.com using this address: https://raq.com/mcp/agent/v1
- Confirm the name and address when the bot shows them, then press Authorise on the connect card it posts.
- Approve access when Raq.com opens in your browser. Raq.com then works in every bot on your account. Check it under Settings, Plugins, Yours.
- If Grok Bot still says it is waiting after you approve, ask it to connect with a Raq.com connect link instead. It sets up the key itself and you approve one link.
- On grok.com: open grok.com/connectors, choose New Connector, then Custom, enter the URL and choose Save & Connect.
- Teams and Enterprise plans: an admin may need to allow Raq.com in the Team Marketplace first.
Coding agents
Claude Code, Codex, Cursor, Grok Build and other agents that run on your computer. Use MCP below, or the Raq.com CLI instructions on this page for terminal workflows.
- Add https://raq.com/mcp/agent/v1 as an HTTP MCP server named Raq.com. Claude Code only accepts letters, numbers, hyphens and underscores in server names, so use raq there: claude mcp add --scope user --transport http raq https://raq.com/mcp/agent/v1
- When the agent asks to authenticate, sign in and approve in the browser tab it opens. In Claude Code, run /mcp and choose raq to start sign-in.
- Coding agents load MCP servers when they start, so one added during a conversation may not appear until the agent restarts. In Claude Code, exit and run claude --continue to return to the same conversation. claude mcp list shows whether raq is connected without printing its token; claude mcp get prints the full Authorization header.
- If the agent cannot open a sign-in page, it can use a Raq.com connect link instead: you approve one link and it adds the key itself. The Claude Code command in the connect link section below does this without printing the key.
- Last resort: sign in to Raq.com, open Settings, then AI Connections, create a token, and add it as a bearer Authorization header. In Claude Code, --header takes several values, so put it after the name and URL: claude mcp add --scope user --transport http raq https://raq.com/mcp/agent/v1 --header "Authorization: Bearer $RAQ_TOKEN", with the token in a shell variable rather than typed into the command.
Raq.com from your terminal
Use Raq.com from your terminal, coding agent or scripts. The CLI and MCP use the same tools and permissions; you can use either or both.
Requires Node.js 22 or later on macOS, Linux or Windows with WSL.
Install the CLI
Run this in your terminal. The installer checks the signed release. Run it again to update.
curl -fsSL https://raq.com/cli/install | bash
Sign in and choose an account
Your browser opens for approval. List your accounts, then replace YOUR_ACCOUNT_SLUG with the account you want to use.
raq login
raq accounts
raq accounts --use YOUR_ACCOUNT_SLUG
raq whoami
Find a tool and use it
Search by what you want to do, read the input schema, then call the tool. This example lists task boards; Task Board must be enabled for the account.
raq search "list task boards"
raq schema task_board_list_boards
raq call task_board_list_boards --data '{}' --json
Give your coding agent the instructions
From your project directory, install guidance for detected agents. To choose one, use raq init codex --project, raq init claude --project or raq init cursor --project.
raq init --project
For CI, supply RAQ_TOKEN through your secret store and set RAQ_ACCOUNT_ID. For a remote terminal, use raq login --paste for hidden token entry or pipe a token to raq login --token-stdin. Never put tokens in command arguments or chat. See the full guide for timeouts, exit codes and shell completion.
Full CLI GuideIf you are the AI agent reading this
Raq.com connects over MCP using OAuth. The person signs in through their own browser, so you never need their credentials. Apps that support bearer tokens can also use a connect link. ChatGPT requires OAuth and cannot use that fallback.
- MCP server
- https://raq.com/mcp/agent/v1
- Plain text guide
- https://raq.com/agent-start.txt
-
Add Raq.com, or say exactly where it goes.
Work out which app you are running in and follow its section. If you can add connectors yourself (Grok Bot, coding agents), add Raq.com now: name "Raq.com" ("raq" in Claude Code, which allows only letters, numbers, hyphens and underscores), using OAuth and the exact connector address above. Put the URL on its own line with no punctuation after it. For a terminal workflow, the person can choose the CLI instructions below instead; an existing MCP connection can stay. Otherwise give the person the one-click link from their app section if it has one (Claude does), or the exact menu path, the name and the URL.
-
Explain the sign-in before it opens.
Tell them a Raq.com sign-in page opens in their own browser. Existing users sign in with a code sent to their email. New users choose Create account and enter their name and email. No password is required. They then approve the connection.
-
Keep going until it works.
If OAuth fails, check the address and retry the connection from the app settings. ChatGPT requires OAuth and cannot use a pasted bearer token: if it still fails, give the exact error and time to Raq.com support. For an app that supports bearer tokens, such as Grok Bot or a coding agent, use a connect link instead: you start it, the person approves one link, and you set up the token yourself. Only if that also fails, ask them to create a token in Settings, AI Connections.
-
Handle credentials safely.
Never ask for passwords or sign-in codes, and do not try to create the account or sign in for them. Put a token from a connect link, or one the person chooses to give you, straight into the connector as a Bearer Authorization header, and never repeat it in the chat.
-
Suggest three jobs, then ask.
Once connected, list the available Raq.com modules, then suggest three specific jobs that suit their business and ask which one to start with. Ask before creating records or changing anything.
Connect link, when OAuth is not available or does not finish
For agents that can make HTTP requests and configure a bearer token, such as hosted bots whose callback stalls or coding agents with no browser. ChatGPT requires OAuth and cannot use this fallback. No credentials are needed to start. The person approves in their own signed-in browser, then you receive a token for the MCP server.
- Start: POST https://raq.com/api/v1/agent-connect/start with JSON {"client_name": "<your app name, such as Grok Bot>"}. The response gives connect_url, user_code, device_code, interval and expires_in.
- Send the person connect_url and user_code in the chat. They sign in to Raq.com if needed, or create a free account, check the code matches and choose Connect. Keep device_code to yourself.
- Poll: POST https://raq.com/api/v1/agent-connect/token with JSON {"device_code": "<device_code>"} every interval seconds. HTTP 202 authorization_pending means keep waiting. 429 slow_down means wait longer between polls. 403 access_denied means they declined, so stop. 410 expired_token means start a new link; links last 15 minutes.
- On HTTP 200 with status connected, add an MCP server named Raq.com (raq in Claude Code) at https://raq.com/mcp/agent/v1 (HTTP transport) that sends Authorization: Bearer <access_token>. The token is shown once and lasts a year. Store it only in the connector configuration. In a terminal, capture it in the same command that polls so it never appears in your output or command history, as the Claude Code command below does.
- Check the connection by listing the Raq.com modules, then carry on with the person. A coding agent may need a restart before the new tools appear; in Claude Code, exit and run claude --continue.
curl -s -X POST https://raq.com/api/v1/agent-connect/start -H 'Content-Type: application/json' -d '{"client_name":"Grok Bot"}'
curl -s -X POST https://raq.com/api/v1/agent-connect/token -H 'Content-Type: application/json' -d '{"device_code":"<device_code>"}'
Claude Code: after starting the link with client_name "Claude Code", run this as your poll every interval seconds. While the link is pending it prints the status. Once approved it replaces any half-added raq server, stores the token and prints "Raq.com connected". The token never appears in the output or in your command.
R=$(curl -s -X POST https://raq.com/api/v1/agent-connect/token -H 'Content-Type: application/json' -d '{"device_code":"<device_code>"}'); T=$(printf '%s' "$R" | sed -n 's/.*"access_token":"\([^"]*\)".*/\1/p'); if [ -n "$T" ]; then claude mcp remove raq --scope user >/dev/null 2>&1; claude mcp add --scope user --transport http raq https://raq.com/mcp/agent/v1 --header "Authorization: Bearer $T" >/dev/null && echo 'Raq.com connected'; else printf '%s\n' "$R"; fi; unset R T
If the connection fails
My app cannot find the server.
Copy the connector address above rather than typing it. Include https and do not add a comma, full stop or spaces. The address is: https://raq.com/mcp/agent/v1
There is no option to add a connector.
Check the app supports remote MCP connectors on your plan. Claude supports custom connectors on every plan, with one on Free. On Team and Enterprise an Owner adds it for the organisation. In ChatGPT, use the web version and check Plugins or your workspace Apps settings; your plan and admin permissions control whether custom apps are available. Grok needs SuperGrok, Teams or Enterprise.
The sign-in page opened but nothing happened afterwards.
Open Raq.com in your app settings and retry the connection, approving in the same browser your AI app opened. In ChatGPT, wait for the tool scan to finish. If it still fails, contact Raq.com support with the exact error and time. Grok Bot and coding agents can use a Raq.com connect link instead.
A colleague connected, but my agent cannot see Raq.com.
The connection is per person. Each team member connects their own AI app once. The workspace and its records are shared, so everyone sees the same results.
Ready to connect your agent?
Copy the prompt, paste it into your AI app and sign in when Raq.com opens.
Want to see what your agent gets first? Explore the Raq.com tools