To connect Claude to 1PC, add https://use1pc.com/mcp as a remote custom connector, authenticate with your 1PC account, then verify a read-only product-state request. Set an explicit Product Owner entry instruction before asking Claude to execute a workflow.
This guide targets Claude's remote connector surface, including its web app and Claude Desktop. It is a setup procedure based on official Claude documentation and the 1PC server contract; it does not report a completed live Claude end-to-end test. For the broader operating method, start with Claude for founders.
Prepare the account and connection
Create your 1PC account and complete the founder profile with resources and constraints that should affect recommendations. You can select an existing product or create one after confirming its name and summary. Use a fictional test product first if you are checking a new connection.
The 1PC endpoint uses Streamable HTTP with authentication. OAuth is the normal starting point; bearer authentication is available for clients that support protected request headers. The MCP authentication reference describes account connections, registration settings and scopes.
Reading requires knowledge:read. Product creation and saving require both knowledge:read and knowledge:write. Authorization scopes and the 1PC plan are separate: write access does not unlock paid instruction catalogs. Claude subscription or organization permissions are also separate from your 1PC plan.
Add the remote connector in Claude
- Open Claude's Customize → Connectors and choose the custom connector option available to your account. Team and Enterprise setup may require an organization owner first.
- Name it 1PC and enter
https://use1pc.com/mcp. - Use OAuth sign-in. Under OAuth client, select Register automatically: 1PC supports dynamic client registration, not Claude's published-identity option. If registration is unavailable, select Use your own OAuth client after registering the actual client and callback through 1PC's advanced MCP settings.
- Complete the 1PC sign-in and consent flow. On a shared Claude organization, each person should connect their own 1PC account through OAuth.
- Enable the connector for the conversation. Confirm that 1PC tools are available before running a product request.
UI labels and eligibility can change. Follow the current Claude remote connector guide for your account. Remote connections originate from Anthropic's infrastructure; a private local endpoint is not a substitute for this public server URL.
Do not paste a personal token into chat. If you deliberately choose bearer authentication, configure it only through a supported credential field and the 1PC token instructions.
Make Product Owner the explicit entry
MCP discovery makes tools callable; it does not install the plugin's native Product Owner skill. Use the following instruction at the beginning of a new product session. You can also retain the short entry rule in Claude project instructions. Refresh the backend requirements each session rather than keeping an old copy of domain guidance.
For each 1PC product workflow, enter Product Owner first.
Load get_skill_instructions with skill_id "product-owner"
and phase "entry". Read get_workspace_context, paginate
list_products and list_product_skills, and resolve the product
and requested task before execution.
Load get_product_context with the selected product_id. Read relevant saved state and revisions. Explain
what exists, what is pending and the intended scope. Keep status
requests read-only and preserve accepted decisions.
For authorized work, select an available catalog skill and load
get_skill_instructions with its skill_id and phase "work".
Load get_task_context for the selected Task when work is requested.
Follow its requirements and applicable checks.
Use actual host tools and keep product_id explicit.
For a requested save, prepare and self-review the scoped Knowledge
or Task update. Keep its scope, exact revision and current Task claim.
Commit the reviewed change, verify saved=true and read back its receipt.
Suggestions do not authorize another workflow or publication.
The catalog returns metadata; load one selected skill through get_skill_instructions. Every User can publish private methods in their workspace. Loading guidance does not install a native Claude skill. See the private skill guide.
If Claude cannot see a named tool, stop at the connection check. Do not accept a plausible response that merely describes what a tool would have returned. The public tool reference explains the schemas; discover actual deployed definitions through the connector.
Verify the first read without saving
Use the connected 1PC tools and the Product Owner entry procedure.
List my accessible products and help me choose the intended one.
After selection, summarize its saved customer context, accepted
decisions and open work. Show the selected product ID and identify
missing or stale context. Do not create or save anything.
Compare the response with the product shown in your 1PC workspace. An empty workspace should be reported as empty; it should not become an invented product history. If several products match, choose explicitly. A successful login is only one step: this read establishes whether the correct account and product state are accessible.
Test one scoped save and a fresh-session read
Once the read is correct, choose a small workflow your plan permits. For example, clarify a fictional idea with Idea Intake. Ask Claude to load its selected skill, complete the brief with your supplied facts, show the proposed result and save it to the destination declared by the returned requirements. This is a content test, not evidence of customer demand.
- Confirm the selected product and authorized save scope. The assistant reads existing content and its revision before replacing it.
- Complete the current part and verify the server receipt plus a read-back. A conflict requires fresh state and reconciliation.
- Open a fresh conversation with the connector enabled and the Product Owner entry instruction.
- Ask for the saved brief and the next unfinished action. Compare with the actual record; do not assume the previous conversation was carried over.
Use the same method before relying on continuity across different AI clients. A saved artifact can be read by another authorized compatible client. Unsaved chats and host processes do not migrate with the MCP connection.
Separate connection failures from workflow limits
| What you see | What to check |
|---|---|
| No 1PC tools | The remote URL, connector enablement and completed authentication. Reading a public documentation page does not authorize the server. |
| Login or consent fails | OAuth registration, redirect settings and current connection credentials. Use the authentication reference. |
| The wrong product is summarized | The selected account and explicit product ID. Paginate accessible products instead of inferring a match from its name. |
| A workflow or private skill is unavailable | Current 1PC entitlement, published skill status and workspace ownership. Reconnecting does not grant paid access. |
| The next session cannot find the result | Whether a save actually succeeded, its product and destination, and the read-back. An unsaved draft remains in the conversation. |
Refer to the MCP error reference for server errors. After the loop succeeds, return to the Claude founder workflow and choose one useful task, such as a weekly product review.
Check the exact connection contract.
Use the 1PC MCP quickstart and authentication reference alongside the current Claude connector settings.
Read the MCP quickstart ↗