Install and connect Docs MCP in Claude Code, Claude Desktop, Cursor, VS Code, Codex CLI, or ChatGPT, then confirm it is working.
This guide walks through connecting Symmetry Docs MCP to your AI assistant and confirming it works. Once connected, your AI assistant can search and cite Symmetry Docs while you work.
Client Support Center credentials. The same sign-in you use to read Symmetry Docs and to track your tickets. Access to the MCP server matches your documentation access.
An MCP-capable AI app. All of the options below are free to download.
The server is HTTP and access-controlled. There is no stdio option and no npm package to install, and because it is hosted there is nothing to keep updated on your side.
Claude Code
Claude Desktop
Cursor
VS Code
Codex CLI
ChatGPT
1
Add the server
claude mcp add --transport http symmetry-docs https://docs.symmetry.com/authed/mcp
2
Sign in
Run /mcp inside Claude Code, then select symmetry-docs from the list to start the sign-in.
1
Open Connectors
Go to Settings → Connectors, then choose + Add, then click Add custom connector.
2
Enter the server details
Name:Symmetry docs
URL:https://docs.symmetry.com/authed/mcp
3
Connect
Click Continue, then on the next screen leave the radio buttons on the Detected options. Under Authentication, use the Sign in now radio button; under OAuth client, use the Register automatically radio button. Click Add.Click Connect. Claude Desktop opens a browser window for you to sign in.
4
Use in conversations
From within a chat, click the + button, select Connectors, and ensure the Symmetry Docs connector is toggled on.
1
Open MCP settings
Open the command palette (Cmd+Shift+P / Ctrl+Shift+P) and select Open MCP settings, or edit ~/.cursor/mcp.json directly.
These steps were verified against the live ChatGPT interface in September 2026. OpenAI moves and renames these settings from time to time, and their own Developer mode guide can lag behind the interface, so expect some drift.
1
Check your plan
OpenAI documents Developer mode as available on Plus, Pro, Business, Enterprise, and Education accounts, on the web. On a Business or Enterprise workspace, an admin may need to allow custom MCP apps before you can add one.
2
Turn on Developer mode
Open Settings → Security and login and switch on Developer mode.
3
Add the server
Go to Plugins, click Browse plugins, then select the plus button, then click Create MCP App, then enter:
Name:Symmetry Docs
Connection (ensure the toggle to the right is set to Server URL): https://docs.symmetry.com/authed/mcp
Authentication: OAuth
Description (optional but recommended): ChatGPT reads this when it decides whether to use the server, so it is worth setting deliberately rather than leaving brief. You can start from this:
Searches and reads Symmetry product documentation for the SymmetryTax Engine, Symmetry Payroll Forms, Payroll Point, Minimum Wage Finder, Calculators by Symmetry,Symmetry I-9, and Symmetry Guides, including their release notes. Use itfor questions about Symmetry APIs, endpoints, request and response payloads,parameters, tax IDs, setup, and product behavior, and cite the page itreturns. It reads the published documentation live, so answers reflect whatis published now. It does not run tax calculations or call product APIs.
4
Create the app
Click Create.
5
Sign in and enable it
Complete the browser sign-in. The server should then be visible under Installed in Plugins. Click the plugin, then Try in chat. From then on, bring it into any conversation by mentioning it by name, for example @Symmetry Docs, or whatever name you gave it.
Each app has a details page in app settings for toggling individual tools and refreshing the app, which is how it picks up a changed description.
Using a different AI app? Add https://docs.symmetry.com/authed/mcp as a custom MCP server in its settings.Popular clients such as Claude, ChatGPT, and Cursor can always complete the sign-in. If your client is not one of those, contact support before you start.
The first tool call opens your browser and prompts you to sign in with your Client Support Center credentials. After you authenticate, the browser tab closes and your AI assistant resumes. Subsequent calls in the same session reuse the cached token.The cached token is valid for 24 hours. After that, the next tool call prompts you to sign in again.
Ask your AI assistant something that only Symmetry Docs would answer, and check that it cites a Symmetry page. Your AI assistant decides whether to show the link the server returns, so if no page appears, add “cite the page” and ask again:
Using the Symmetry docs, what are the three values signForm accepts in the SPF API, and what does each one produce?
A correct answer names PREVIEW, SIGN, and SIGN_EXTERNALLY, and explains that PREVIEW is the default.
What a working answer looks like
signForm is an attribute on the /fillPdf endpoint, and it defaults to PREVIEW, so if you are expecting a signed form you have to ask for one explicitly.
PREVIEW: an unsigned preview. The SSN (U.S.) or SIN (Canada) is masked and all form fields are flattened. Intended for letting the employee review the form before committing.
SIGN: a completed, fully executed form. The signature line carries the employee’s name plus a date and time stamp, the SSN or SIN is unmasked, and all fields are flattened. The timestamp needs a timezone, supplied as an IANA identifier such as America/Chicago. Without one, SPF signs in UTC.
SIGN_EXTERNALLY: a completed form with an unmasked SSN or SIN but no electronic signature or date, for use with an external signing tool such as DocuSign. Everything is flattened except the signature and date fields.
Two pages cover this: Interpreting SPF API responses has the authoritative breakdown plus the nonstandard signature fields (MO101 to MO103, NJ102), and Form output has the same three modes in table form with use-case guidance.
The same answer in Claude Desktop.
Then check that it can read a full page rather than working from a search snippet:
Read the whole STE licensing page and list every credential type, and which interface uses each.
Expect three credential types across five interfaces.
What a working answer looks like
Three credential types, mapped across five interfaces.
STE license file (ste-license.dat): authorizes the engine for an on-premise install, and is part of the licensed distribution. Downloaded from the Download Center as a ZIP with “License” in the name, then placed in the root of your STE directory, or supplied via the STE_LICENSE_KEY environment variable, which is checked first. The engine will not run without it.
API key: per client and product, issued by Symmetry, sent as the raw value of the Authorization header on every request. Staging and production keys are separate, and mixing environments fails.
Client Support Center credentials: user-level sign-in, where you authenticate as yourself rather than with a shared service key.
Interface
Credential
Hosted API
API key
Tax Logic API
API key, same key model as hosted
On-premise SDK
STE license file plus API key
STE MCP
Client Support Center sign-in
Tax Logic Chat
Client Support Center sign-in
On-premise installs also use an API key for the Symmetry Location Service, which handles address geocoding, set as SLS_API_KEY in ste.conf. That is a configuration detail rather than a second license, and on the hosted API it is handled for you.
The same answer in Claude Desktop.
If no page appears even after you ask it to cite one, or it cites something that is not a Symmetry docs page, it is answering from general knowledge and the server is not connected. Check that sign-in completed, then see troubleshooting.
That’s the whole setup. Your AI assistant can now search and cite Symmetry docs in any conversation, and sample prompts has questions to try, grouped by role.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.