Tapestry in your chat app

Ask your assistant what’s doable now, turn a goal into linked steps, or update a task without leaving your conversation. MCP connects the assistant to the same tasks, workspaces, and graph you use in Tapestry.

You use your existing Tapestry account. You do not need to install a local server, generate an API key, or give your password to your assistant.

Connect

Use this remote MCP server URL:

https://tapestry.pyrite.ai/api/v1/mcp

Add a custom MCP server or connector in your chat app and name it Tapestry.
Paste the URL above. Choose OAuth authentication and the client’s published identity / Client ID Metadata Document option when offered. Tapestry does not currently support automatic dynamic client registration.
Sign in on the Tapestry page and review the connection’s access. Choose a workspace, or all workspaces if your plan allows it. Task changes are optional and require a client that requests write access.
Finish connecting, then enable or select Tapestry in your conversation.

ChatGPT

On the web, open Plugins → Add custom MCP server, enter the URL, and choose OAuth with Client ID Metadata Documents (CIMD), rather than supplying a client secret. Install the resulting plugin and select it with @Tapestry in your conversation. Availability depends on your account and workspace policies. See OpenAI’s setup instructions.

Claude

Open Customize → Connectors → Add custom connector, enter the URL, and choose Sign in now with Use Claude’s published identity. Enable Tapestry for the conversation after connecting. In managed organizations, an owner may need to add the connector first. See Claude’s setup instructions.

Other MCP clients

Use Streamable HTTP with OAuth. The client must support Client ID Metadata Documents or a preregistered OAuth client; a client that only supports dynamic registration cannot connect through this flow. For scripts that need a manual bearer token, see Delegates.

Choose the right access

Start with one workspace and read-only access if you just want help planning.

Choice	What it means
One workspace	Only that workspace’s visible tasks and related context are available.
All workspaces I can access	Includes workspaces you join later; access ends when your membership ends. Free plans are limited to one workspace.
Allow task changes	Lets the assistant create, edit, assign, complete, link, and archive work where you have editing permission. Leave this unchecked for read-only access.

A connection never grants more access than you have yourself. Even with task changes enabled, hosted MCP cannot delete tasks, invite people, change sharing or billing, or manage workspaces and credentials.

Content retrieved through MCP goes to the chat app you connected. Read-only is still access to your task content, so choose the scope thoughtfully and review the app’s tool approvals.

Things to try

Be explicit that you want the assistant to use Tapestry, especially if you have several task apps connected.

“Use Tapestry to show the tasks assigned to me that I can actually start now.”
“What is blocking #42? Which following tasks have a deadline?”
“In my Launch workspace, make a plan for the release. Show me the steps before creating and linking them.”
“Assign #42 to me—not to your delegate—and snooze it until Friday.”
“Show the columns on my Planning board, then move #42 to Review.”
“Find our onboarding template and preview it for Alex before inserting it.”
“Create a reusable release template in Launch, with preparation before shipping and a project-name variable.”
“Save #12, #13 and #14 as an onboarding template, keeping the links between those tasks.”
“Copy the published onboarding template to HR, and leave the copy as a draft for review.”
“Archive the old release template without touching tasks already created from it.”
“Show the previous insertions of our onboarding template and their versions.”
“Post a comment on #42 saying the draft is ready for review.”
“Archive #42, but don’t delete it. Show me what will happen to its dependencies first.”

You can also ask about task notes and discussion, tags, attachment metadata, workflow statistics, and task notifications. Posting comments requires task changes to be enabled and follows your normal notification preferences. MCP does not upload or download attachments or send direct messages.

Template creation and editing require task changes and workspace editing permission. A valid template created with steps is ready to use immediately. Later edits remain a draft until you ask to publish them; existing tasks created from the template do not change. The assistant must read the entire draft before replacing it, and Tapestry refuses edits or publishing if someone changed it in the meantime.

You can capture existing tasks from one workspace into a template without changing the source tasks; assignments and dates are left behind. Copies start as drafts: duplication in the same workspace uses the current draft, while copying elsewhere uses the published version and respects the source workspace’s export restrictions. Archiving a template preserves its content and past insertions; unarchiving makes it available again. Insertion history shows the version used and how many non-deleted tasks still live in the original workspace, not saved variable bindings.

Use a task’s link or qualified reference when a title is ambiguous. The assistant should ask which task you mean instead of guessing. Results may be paginated or shortened; ask it to retrieve the remaining pages when you need a complete list.

Assign to yourself or to the assistant

Connecting creates a Delegate that identifies the integration. “Assign this to me” means your user account; “claim this for your delegate” means the connected assistant’s Delegate. Those are distinct assignees, and the Delegate’s identity remains on changes it makes.

Assigning work does not start an autonomous background worker. The assistant still needs to read its assignments and act when you ask it to. See the agent operating guide for instructions to give a longer-running agent.

Archive, don’t delete

Archived tasks stay in the archive indefinitely and can be brought back. By default, archiving connects the task’s prerequisites to its dependents; both archive healing and undoing healed links require editing permission on the affected tasks. You can ask to archive without healing if you do not want new bypass links. Unarchiving does not restore deleted tasks.

Manage or troubleshoot a connection

Open Settings → Delegates to inspect, pause, or revoke the connection. Pausing is reversible; revoking stops its credentials from working. To choose different access, reconnect and approve a new grant. Connections and manual Delegates share your plan’s Delegate limit; Tapestry offers replacement when the limit is reached.

No tasks appear: check the connected account, workspace scope, and whether you asked for Now or all tasks. Now excludes work that is not currently doable.
Changes are refused: the connection may be read-only, the chat app may have disabled that tool, or you may lack editing rights. Reconnect with task changes enabled when appropriate; it cannot bypass workspace permissions.
No “Allow task changes” option appears: the client requested only read access. Refresh its server metadata and reconnect so it discovers the available write scope. If the client lets you configure OAuth scopes, request tapestry:read tapestry:write; enabling changes still requires your explicit approval on Tapestry’s consent page.
A dependency or archive fails: another task in the relationship may be outside the granted workspace, or the proposed link would create a cycle. Use a suitable scope or revise the relationship.
Sign-in fails: confirm the exact URL and OAuth/published-client-identity setting. Do not select “No authentication” or automatic registration.
The connection needs sign-in again: connections renew automatically and can stay connected while in use; renewal access expires after 365 days without renewal. A pause, revocation, lost workspace access, or failed client renewal can interrupt this sooner. Older connections created without renewal access need one reconnection after the update. Separate machine connections do not sign each other out, but copying the same refresh credentials between installations can trigger replay protection. Manage or reconnect the affected connection in Settings → Delegates.
An action timed out: check whether it already happened before asking to create it again. Task and template creation are not automatically deduplicated on retry.
A new tool is missing: Tapestry sends tool-catalog change notifications to listening clients and a refresh signal when they reconnect. Your chat app must support these notifications; refresh its tools or reconnect if it keeps an old catalog. Existing access stays the same—new permissions still require consent.

Menu labels can change; the linked vendor setup guides are the current reference for your chat app.