Search and Update Jira and Confluence Through Your Muse

Through an AnythingMCP custom connector, your muse can work in Jira and Confluence: search work items and pages in plain words or with filters, read one item, create and edit work items, and add comments.

What it does

The connector adds 193 tools through the official Atlassian Rovo MCP server, covering Jira, Confluence, and plain-language search across your Atlassian apps. For Jira, ask for work items by project and status, read one item with its priority and assignee, create a task, bug, story, or epic, edit fields, move an item to a new status, and add a comment. For Confluence, search pages, read one page, and write pages where your token allows it. Tools that delete work or change project settings start switched off.

How to use it

1. Start an AnythingMCP account and add the Atlassian connector.
2. Ask an Atlassian admin to turn on API token sign-in for the Rovo MCP server. Without that step, every call is refused.
3. Signed in as the person the muse should act as, create a scoped API token with read, write, and search scopes for Jira, Confluence, and Rovo search. Copy it right away; it shows only once.
4. Paste your Atlassian email and the token into the connector.
5. In Muse, open Settings, then Connectors, and add a custom connector with the MCP server address AnythingMCP gives you. Sign in and approve.
6. Start with a plain-language search, such as open items assigned to you, and check them in Jira.

What you need

• A Muse account that can add custom connectors
• An AnythingMCP account with the Atlassian connector added
• An Atlassian account where an admin has turned on API token sign-in, plus a scoped API token

What to watch for

• Every call runs with the token owner's permissions. Use an account that sees only the projects the muse should reach: anything that account can open, the muse can read.
• Plain-language search draws on your organization's Rovo credit pool, up to 10 credits a call. Broad searches add up, so ask one clear question at a time.
• A sign-in error usually means the admin step was skipped, or the email and token do not belong together. A scope error means the token lacks that app's scope; a new token fixes it.
• Editing a work item changes the record your team works from. Read it back in Jira first.
• This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.