Example · ships with Charlie
Atlassian
Jira and Confluence in Charlie, from an extension that declares no tools at all. It signs you in to Atlassian's own server, and that server brings the tools.
What's in the folder
atlassian/
├── manifest.json the description file
└── build/
└── Settings.js the Connect / Disconnect panel
The manifest
{
"name": "atlassian",
"description": "Atlassian — search, read, and edit Jira issues and Confluence...",
"version": "0.1.0",
"developer": {
"name": "Andy Dale",
"contact": "(hidden on this page)"
},
"tier": "core",
"connections": [
{
"name": "atlassian",
"authType": "oauth2-discovery",
"transport": "mcp-server"
}
],
"settings": {
"component": "./build/Settings.js"
}
}| Line | What it plugs into |
|---|---|
"connections" | 2 · Connections. The mcp-server transport means Atlassian's hosted server supplies the tools once you're signed in. |
"settings" | 4 · Settings. The panel where you connect or disconnect. |
Ideas to borrow
- If a service already runs its own MCP server, your extension can be little more than a sign-in. You don't write or maintain the tools.
- The tools appear in Charlie only while some switched-on extension claims the connection, so switching this extension off removes them.