Connect AI apps
Claude, ChatGPT, Claude Code and Codex can read and update your issues, projects and cycles, and see production errors and services. They connect over MCP with a sign-in, so there's no token to copy.
Every app uses the same URL, your ProjectVerse address followed by /api/mcp:
https://projectverse.kemojallow.com/api/mcpConnecting asks you to sign in to ProjectVerse, pick one workspace and click Allow. The app then works in that workspace as you, with your role. It can't change your account or workspace settings. To use several workspaces, connect once per workspace.
Claude (Desktop, claude.ai, mobile)
- Customize → Connectors (in the sidebar; older versions: Settings → Connectors), then Add custom connector.
- Name it
ProjectVerseand paste the URL. Click Add. - Click Connect, sign in to ProjectVerse, pick the workspace, then click Allow.
- In a chat, open the tools menu and make sure ProjectVerse is on.
The connector syncs to Claude Desktop and the mobile apps.
ChatGPT (Desktop, web)
- Settings → Apps & Connectors → Advanced settings, then turn on Developer mode.
- Create a connector. Name it
ProjectVerse, paste the URL as the MCP server URL, and set Authentication to OAuth. - Sign in to ProjectVerse, pick the workspace, then click Allow.
- In a chat: + → Developer mode → ProjectVerse.
Claude Code
Install the plugin. It adds the server, a skill that teaches Claude Code to track its work in
ProjectVerse, and /projectverse:status.
/plugin marketplace add kemojal/projectverse
/plugin install projectverse@projectverse
/mcp → projectverse → AuthenticateWithout the plugin, add the server yourself:
claude mcp add --transport http projectverse https://projectverse.kemojallow.com/api/mcpThen run /mcp → Authenticate.
For another ProjectVerse instance, set PROJECTVERSE_URL (for example http://localhost:3000)
before starting Claude Code. The plugin uses it instead of the default.
Codex
codex mcp add projectverse --url https://projectverse.kemojallow.com/api/mcpCodex opens the browser to sign in. Later, codex mcp login projectverse signs in again.
Tell agents where work goes (optional)
In a code repository, add an AGENTS.md (Codex reads it; Claude Code reads it through a
CLAUDE.md containing @AGENTS.md). In it, name the team key and project, and say how to
track work, for example:
## Project tracking: ProjectVerse
Workspace `cutwords`, team key `CUT`, project `cutwords`. Before starting a task, find or create
its issue; move it to in_progress, comment progress, and set it to done with a summary. Open
issues for bugs you notice. Put the identifier (CUT-12) in commit messages.What you can ask
- "What's in progress on the cutwords project?"
- "Create a high-priority bug in CUT: export fails for videos over 10 minutes."
- "Move CUT-3 to done and comment what changed."
- "Post a project update on cutwords: on track, shipped the editor."
- "Show unresolved production errors and the stack trace of the top one."
- "Which services are down or slow?"
Manage connected apps
Your connected apps are listed under Settings → Connected apps, one row per app and workspace, with when each was last used. Disconnect stops an app at once.
- Leaving a workspace disconnects your apps there.
- Connecting and disconnecting are recorded in the audit log.
API tokens: for scripts and older tools
Tools without a sign-in flow can use an API token instead: Settings → API tokens, sent as
Authorization: Bearer pv_…. A token is limited to one workspace, like a connection. Revoke
tokens you no longer use.
Troubleshooting
- The app says it can't connect or find an authorization server. Check that
https://<your ProjectVerse>/.well-known/oauth-authorization-servershows JSON. If it shows the login page instead, the server is running an older version: redeploy. Self-hosters must setAPP_URLto the public address, because it's what the app is told to sign in with. - "This connection request isn't valid". The app's registration is stale. Remove ProjectVerse from the app and add it again.
- The app worked, then stopped. Someone may have disconnected it in Settings → Connected apps, or you may have left the workspace. Connect again.
For developers, the protocol details (discovery, registration, tokens) are in
api.md.