ShipWoven in your AI assistant
One connector, ShipWoven, for Claude, ChatGPT, Cursor and other assistants that speak MCP. Ask about your products and their setup, issues, Jira tickets, daily reports and the roadmap, and get things done, always as yourself.
Before you connect
- You need a ShipWoven account in your organisation’s workspace (for example
yourcompany.shipwoven.com). - A super admin of your organisation turns assistants on, in the portal under Integrations → AI assistants (MCP), and chooses what they may read and do. Reading starts on; acting stays off until they allow it.
Connect
- In your assistant, add a connector. In Claude: Settings → Connectors, find ShipWoven, or add a custom connector with the address
https://mcp.shipwoven.com/mcp. - Press Connect. ShipWoven opens: type your organisation’s name (the first part of your ShipWoven address), and sign in.
- See what the assistant will be able to read and do, and press Allow.
Sign-in uses OAuth 2.0 with PKCE. Your password never reaches the assistant: it holds a token for you in your organisation, valid 8 hours and renewed for up to 90 days. You can disconnect it at any time in the portal, under Integrations → AI assistants; a super admin can disconnect anyone’s.
What it can do
Everything runs as you, through the same checks as the portal: you only see and do what you can in ShipWoven, and only what your organisation allows assistants to do.
Reading
| Tools | What for |
|---|---|
whoami | Who you are in ShipWoven, your organisation, and what the assistant may read and do |
list_products · get_product | Your products and their setup: website, repositories, mobile apps and store accounts, environments, databases, domains, services and accounts (credentials by name only, never a secret) |
list_issues · get_issue | Issues reported in ShipWoven, with their answers, stage, assignee and history |
list_jira_tickets · get_jira_ticket | Jira tickets synced into ShipWoven; one ticket read live from Jira (when your organisation has Jira connected) |
list_reports | Daily reports you can see, with their answers |
get_roadmap | What the company works on now, its epics and progress, and the year roadmap |
Acting, as you (when your organisation allows it)
| Tools | What for |
|---|---|
create_issue · get_issue_form | Report an issue, answering your organisation’s issue form |
comment_on_issue · assign_issue · move_issue | Comment on an issue, assign it (to yourself, someone else or nobody), or move it to another stage |
comment_on_jira_ticket · change_jira_status · assign_jira_ticket_to_me | Comment on a Jira ticket, change its status, or take an unassigned one; sent to Jira (when your organisation has Jira connected) |
submit_report · get_report_form | Submit your daily report |
Nothing can be deleted through the connector.
Try asking
- “What are we working on now, and how far along is each epic?”
- “Which issues are assigned to me and still in QA testing?”
- “Where is the Acto product deployed, and which database does its live environment use?”
- “Summarise yesterday’s daily reports from the mobile team.”
- “Report an issue on the Website product: the sign-up button does nothing on Safari.”
Your data
The connector keeps nothing: it passes each request to your organisation’s workspace and returns the answer to your assistant. What your assistant does with the answers is governed by your assistant’s provider. Credentials only ever show their name, and encrypted sections (credentials, finance, legal documents) are never sent. Details are in our privacy policy.
For super admins
- Turn it on or off for the whole organisation, and choose what assistants may read and do: Integrations → AI assistants (MCP).
- See every connected assistant, who connected it and when it was last used, and disconnect any of them, on the same card.
Help
Questions or problems: info@shipwoven.com. Security issues: info@shipwoven.com.