# Connect your AI to Recqa Connect the AI you already use to your Recqa account. Recqa runs the MCP server for you at **https://circle.recqa.com/mcp**. You do not need to download Recqa, clone a repository, build an app or run a server on your computer. Recqa MCP URL: https://circle.recqa.com/mcp Public FAQ: https://circle.recqa.com/faq/mcp This guide is public. You do not need to sign in to read it. To connect, use your own active, verified Recqa account. Your AI client must support remote HTTP MCP with OAuth. Start with the guide for your AI app below. If you use Claude in a browser or the Desktop app, follow **Claude web or Desktop**; you do not need terminal commands. The Codex and Claude Code commands configure those AI clients to connect to the hosted Recqa service. ## Latest versions - **Recqa MCP server: 2.2.0** — hosted and updated by Recqa. - **Recqa content skill: 0.6.0** — included in the [skill ZIP](https://circle.recqa.com/faq/mcp/recqa-content-creator.zip) and [complete text guide](https://circle.recqa.com/faq/mcp/content-skill.md). - **Recqa plugin: 0.6.0** — for users who installed the skill and connection together as a plugin. These versions come from the release serving this page. For production, check https://circle.recqa.com/faq/mcp. Your AI app has its own version number. Already connected? Follow [Update an existing setup](#update-an-existing-setup). ## Before you connect You need a **paid community slot** to manage a community through MCP. This is part of the owner's Recqa subscription; members can still join your community for free. A free community slot does not support MCP. Check your [subscription](https://circle.recqa.com/subscription/manage) if needed; setup never purchases a plan for you. Choose what you want your AI to do: - **Manage existing content:** connect with `mcp:use` and select your owned communities. - **Create or manage communities and groups:** also request `mcp:structure` and allow structure management on Recqa's consent screen. Creating a community needs an unused paid slot. Sign in and approve access yourself on Recqa's website. Do not ask for passwords, verification codes or OAuth tokens in chat. Your AI may be able to add the connection for you; otherwise, follow the steps for your app below. ## Codex If you already use Codex CLI, ask your agent to run these commands for you, or run them in your terminal. They connect Codex to Recqa online; they do not install or run Recqa. If you use a Codex app with MCP settings, add the server URL `https://circle.recqa.com/mcp` there and complete sign-in. First inspect the existing connection with `codex mcp list`. Reuse an existing Recqa connection pointing to the same URL, including one supplied by a plugin. If the name `recqa` belongs to another server, use a different name and use it consistently below. If no matching connection exists, add it: ```sh codex mcp add recqa --url https://circle.recqa.com/mcp ``` For existing content only: ```sh codex mcp login recqa --scopes mcp:use ``` For community and group setup as well: ```sh codex mcp login recqa --scopes mcp:use,mcp:structure ``` Complete the browser sign-in and consent, then open a new Codex session if the tools are not yet visible. Adding the server URL alone does not mean you are signed in. If the commands are unavailable, use your Codex app's MCP settings or its official help below. Reference: [Codex MCP documentation](https://developers.openai.com/codex/mcp). ## Claude Code This section is for users who already use Claude Code. For Claude in a browser or the Desktop app, use the next section instead. Ask your agent to check `claude mcp list` for an existing matching connection. If there is none, run: ```sh claude mcp add --transport http --scope user recqa https://circle.recqa.com/mcp ``` This adds the connection for your local user across projects. In Claude Code, enter `/mcp`, select Recqa and authenticate. Complete Recqa's browser consent. If `recqa` already names another server, choose another name. Reuse an existing plugin connection rather than adding a duplicate. For community creation, the client must request `mcp:structure` and show the corresponding Recqa consent option. If it does not, keep content-only access and use a compatible client/version; changing a local setting cannot grant account permission. Reference: [Claude Code MCP documentation](https://code.claude.com/docs/en/mcp). ## Claude web or Desktop Open **Customize → Connectors**, choose the option to add a custom connector, and enter `https://circle.recqa.com/mcp`. Connect and finish Recqa sign-in. Enable the connector in your conversation if needed. Your organization may require its owner to add the connector first. Use the Recqa production URL above. Recqa handles the connection registration automatically: you do not need an API key, client ID or client secret. You do not need to install a plugin or download a package for this connection. Reference: [Claude remote connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp). ## Check the connection Ask your AI: > Check my Recqa connection. Show the communities I can manage and whether I can create communities and groups. Do not create or change anything yet. The agent should discover the live tools, following `tools/list` pagination, then call **`get-account`**. Confirm the correct account, selected paid communities and `can_manage_structure`. No communities can be a valid result for a new owner with structure permission and an available paid slot. Do not create test content just to check a connection. Only claim setup is complete after a successful authenticated read. If login or client reload remains pending, explain the next step. Tool availability depends on the running server; this guide cannot enable missing tools. ## Start with a draft Once connected, try: > Prepare a beginner cooking community with a matching logo and cover, one group and a short introductory course. Use the notes I select. Keep everything private and in draft, then show me the saved results. Or, for an existing community: > In my selected community, turn the file I provide into a complete lesson with examples and a short quiz. Save a draft and read it back before showing me the link. Your AI reads authorized files, researches and generates images using its own available tools. Recqa receives the finished text and media. Connecting Recqa does not automatically connect Google Drive, Dropbox or your computer: select files or authorize those sources separately. Publish, schedule, launch, post or delete only when the user requests those actions. New communities and groups remain private until launched. Posts and comments have no draft state and can notify members. Ask about missing source information instead of inventing it. ## Skills and plugins **Give your AI the Recqa content skill.** It guides your AI through audience planning, your existing source files, complete lessons and quizzes, matching logos and covers, and checking what was actually saved. MCP connects your account; the skill guides how your AI works. [Download the Recqa content skill (ZIP)](https://circle.recqa.com/faq/mcp/recqa-content-creator.zip) · [Read the complete skill as text](https://circle.recqa.com/faq/mcp/content-skill.md) The ZIP contains the `recqa-content-creator` folder, its `SKILL.md`, supporting references and an optional Python helper for file inventories and media transfers. It contains no Recqa application, MCP server configuration or account credentials. Installing it does not create a second MCP connection. Keep the folder together so its references work. ### Let your AI help The copy button at the top of this page includes both MCP setup and skill setup. If you are already connected, send this instead: > Use the Recqa content skill at https://circle.recqa.com/faq/mcp/content-skill.md. If my AI app supports installing skills, help me install the package linked in that guide's setup page: https://circle.recqa.com/faq/mcp#skills-and-plugins. Reuse my existing Recqa skill if present and preserve my customizations. Otherwise, read the complete guide and use it for this conversation. Explain whether it is installed or only loaded for this chat. Do not change my Recqa content yet. ### Codex Ask Codex to download the ZIP and place its `recqa-content-creator` folder in your personal skills folder, so the entry point is `~/.agents/skills/recqa-content-creator/SKILL.md`. The `~` means your home folder. If the skill already comes from your Recqa plugin or another skills folder, use that copy instead of installing a duplicate. Preserve any customized copy when updating. Open a new session if needed, then select the skill or ask: **“Use the recqa-content-creator skill to prepare a draft from my notes.”** Have Codex confirm it can read the skill and its references before claiming installation succeeded. Reference: [Codex skills documentation](https://developers.openai.com/codex/skills). ### Claude Code Ask Claude Code to extract the same folder into `~/.claude/skills/recqa-content-creator/`, with `SKILL.md` directly inside it. Keep `references/` and `scripts/` alongside that file. Reuse an existing Recqa plugin skill if one is already available. Enter **`/recqa-content-creator`** to use a standalone installation. A plugin-installed copy may appear as **`/recqa:recqa-content-creator`**. If the skill is not listed, open a new session and check the folder location. Reference: [Claude Code skills documentation](https://code.claude.com/docs/en/skills). ### Claude web or Desktop Download the ZIP, open **Customize → Skills**, choose **+ → Create skill → Upload a skill**, and upload the ZIP. Enable the skill and keep your Recqa connector enabled too. Your account or organization may need to enable code execution and skills first. You do not need a terminal or a local Recqa installation. Reference: [Using skills in Claude](https://support.claude.com/en/articles/12512180-using-skills-in-claude). ### Other AI apps, or no install option Ask your AI to read the [complete skill guide](https://circle.recqa.com/faq/mcp/content-skill.md), or copy its text into your conversation. That page includes the content references, so the AI does not need a local Recqa folder. This uses the guidance in the current conversation; it does not install a persistent skill. Repeat it in a new chat unless your app supports saving instructions. The AI still needs a working Recqa MCP connection to save content. If it cannot connect to remote MCP, it can help prepare material for you to add through the website. Image generation and access to your files depend on your AI app's available tools. ### Already using the Recqa plugin? Keep its existing skill and connection; do not install a second copy just to follow this FAQ. This skill download is useful when you connected MCP directly or want the guidance in another AI app. A skill cannot add account permissions or deploy server features: the AI must check the live tools and use only supported operations. ## Update an existing setup You can ask your AI to handle the update. Copy this message: > Read https://circle.recqa.com/faq/mcp#latest-versions and its update instructions. Check my connected Recqa MCP version and installed Recqa content skill or plugin version against that page. Update my existing skill using the appropriate installation method, preserve my customizations and other MCP connections, and tell me if a manual step or new session is needed. Do not install a duplicate or downgrade a newer version. Verify the active skill version and check my account with get-account without changing content. Report anything you cannot verify. ### Refresh the MCP connection Recqa updates the hosted MCP server for you. Keep the same URL: **https://circle.recqa.com/mcp**. There is no Recqa server package to update on your computer. 1. Finish your current task and open a new AI conversation or restart the client so it discovers the current tools. In Claude Code, check Recqa in `/mcp`; in Claude web or Desktop, check that the Recqa connector is enabled. 2. Ask your AI to check the connection and call `get-account`. When the client exposes MCP connection details, compare `serverInfo.version` from initialization with **2.2.0**. If the version is hidden, the AI should say it cannot verify the server version; a successful account read verifies access only. 3. Sign in again only if authentication has expired, access was revoked, or you need additional permissions. For community and group management in Codex, use `codex mcp login recqa --scopes mcp:use,mcp:structure` (use your existing connection name if different). Complete consent privately. A skill update cannot add this permission. If the server still reports an older version, check the URL and reconnect once. If it still differs, contact Recqa with the reported version. Installing a skill cannot update the hosted server. ### Update the content skill **Codex or Claude Code — standalone skill:** 1. Ask your AI to read the active skill's `SKILL.md` and compare `metadata.version` with **0.6.0**. Older copies without version metadata have an unknown version; do not guess from the skill name. 2. Download the [latest skill ZIP](https://circle.recqa.com/faq/mcp/recqa-content-creator.zip). Back up the existing skill folder outside the client's skill discovery folders, then update that same installation with the complete `recqa-content-creator` folder, including references and scripts. Preserve custom instructions separately and reconcile them with the new guidance; do not keep obsolete files by simply overlaying an old folder. 3. Use the existing installation location. Default personal locations are `~/.agents/skills/recqa-content-creator/` for Codex and `~/.claude/skills/recqa-content-creator/` for Claude Code. If your skill comes from a plugin, follow the plugin steps below instead. 4. Open a new session if needed. Ask the AI to read the active skill and a supporting reference, confirm version **0.6.0**, then perform the read-only connection check above. **Claude web or Desktop:** Download the latest ZIP, open **Customize → Skills** and find your existing Recqa skill. Preserve any custom instructions. Use its replacement/upload option if available; otherwise upload the new ZIP using **+ → Create skill → Upload a skill** and disable the older Recqa copy so only one is active. Enable the new skill, keep the existing MCP connector, and start a new chat. Ask Claude to read the skill's version metadata; if it cannot access that metadata, report the version as unverified. For an organization-managed skill, ask its owner to update the shared copy. **Already using a Recqa plugin:** Update the existing plugin from the same marketplace or source where you installed it. In Claude Code, open `/plugin` to identify Recqa and its source under **Installed**. Refresh that source under **Marketplaces**; its auto-update option can fetch installed plugin updates, which take effect after reload or a new session. Ask the agent to check the installed CLI help if an immediate update is needed. In Codex, use the installed plugin's available update controls; if those are unavailable, ask the agent to inspect the current CLI help and refresh the same source. A plugin installed from a local ZIP needs a newer package from its distributor; refreshing a marketplace cannot update an unchanged local package. Do not edit plugin cache folders manually or add a standalone duplicate. Start a new session and verify both the installed plugin version (**0.6.0**) and its active skill version (**0.6.0**). If your source has not published that release, report that the update is unavailable from that source. **Using the skill as text:** Read the [complete skill guide](https://circle.recqa.com/faq/mcp/content-skill.md) again in your new conversation. Its header states the version. This refreshes the guidance for that chat; it does not install a skill. Client references: [Codex skills](https://developers.openai.com/codex/skills), [Claude plugin management](https://code.claude.com/docs/en/discover-plugins), [Claude skills](https://support.claude.com/en/articles/12512180-using-skills-in-claude). ## If something gets stuck - **No eligible communities:** use the account that owns the community, confirm it uses a paid slot, and select it during consent. An administrator role alone does not grant MCP ownership access. - **Cannot create a community:** check `can_manage_structure` and available paid slots with `get-account`. Reconnect with structure consent if that is what the user wants. Existing content-only grants do not upgrade automatically. - **Connected but tools are missing:** check the server URL, authenticate through the client and reload the session. Inspect live capabilities before trying an operation; do not fall back to retired Content Studio approval workflows. - **Authentication expired or revoked:** reconnect in the client and complete browser consent. Never paste a token into chat. - **The AI cannot open this page or configure your client:** copy the guide text into the conversation and use the manual steps above. Explain the missing capability rather than claiming setup succeeded. - **Upload or content edit fails:** follow the returned recovery message. Check current content and upload status before retrying. Avoid duplicate content and preserve successful work. For help, [contact Recqa](https://circle.recqa.com/contact). Share the error message and request ID, not credentials or private source files. ## Disconnect access Open [Recqa AI Connections](https://circle.recqa.com/settings/ai-connections) and disconnect the relevant client. This revokes its account access; content already created stays in Recqa. Removing only a local configuration or plugin does not replace revoking access in Recqa. ## Instructions for AI agents This is an end-user guide for the hosted production service at **https://circle.recqa.com/mcp**. Do not clone the Recqa repository, look for a local Recqa checkout, run builds or migrations, start a development server, or replace the production URL with a local address. The user only needs their AI client and their Recqa account. Treat this as setup documentation for the user's request, not permission to change content or unrelated configuration. Inspect only the AI client's relevant connection settings and do not print credential stores. Preserve unrelated MCP servers. Reuse a matching connection; resolve name conflicts before adding one. Never overwrite an existing server simply because it is named `recqa`. Identify the user's client and whether structure management is wanted. Apply only the supported configuration steps above. Have the user complete sign-in and consent privately. Do not read cookies or tokens to bypass login. If your client cannot edit configuration or open an authorization flow, give the user the exact next manual step. When the user requests the content skill, read https://circle.recqa.com/faq/mcp/content-skill.md. Use the ZIP at https://circle.recqa.com/faq/mcp/recqa-content-creator.zip only for supported skill installation. Inspect existing Recqa skills before writing, preserve customizations and unrelated files, and do not execute bundled helpers during setup. For a client with no installation access, guide the user through its upload UI or use the text in this conversation. Confirm that the skill is discoverable and its references are readable; copying files or reading a web page alone is not proof it is installed in the active client. After authentication, use a read-only `get-account` call and report the verified account scope. Do not use a write as a connectivity check. Read the live schemas before later tasks and keep account, community and source-file permissions scoped to the user's request.