AI agent
MCP Server + ProjectMind
Technical reference for ProjectMind MCP
One HTTP MCP endpoint powers every agent guide. Full setup, auth, and tool tables live in the MCP documentation.
Example chat
via ProjectMind MCP · MCP Server
How to connect MCP Server
- Add the server URL to OAuth-capable clients: https://projectm.dev/api/mcp
- Use Authorization: Bearer with imk_/imgk_/imbk_ keys when OAuth is unavailable.
- Append ?projectSlug=your-slug for multi-project accounts.
- Call tools/list after connect; confirm mutating tools match your role.
- Read the full MCP docs for client-specific JSON snippets and OAuth details.
ProjectMind MCP server URL
https://projectm.dev/api/mcp
Cursor (.cursor/mcp.json)
{ "mcpServers": { "imemory-api": { "url": "https://projectm.dev/api/mcp", "headers": { "Authorization": "Bearer imk_your_project_api_key_here" } } } }
OAuth sign-in is recommended for chat clients. Project API keys (imk_…) work when the client cannot open a browser. Confirm before startEpicExecution, enqueueAgentJob, or deleteTask.
What you can do with MCP Server
OAuth and keys
Browser OAuth for assistants; project API keys for headless HTTP clients.
Task & epic surface
Tasks, epics, stages, initiatives, and execution controls.
Agent operations
Profiles, enqueueAgentJob, delegations, and job lifecycle tools.
Monitoring
Health checks, stats, executive summary, and improvement proposals.
MCP tools and prompts
This page is a marketing overview. For client setup tables, auth details, and the complete tool list, see MCP server documentation.
Tasks & current work
listTasks · getCurrentTask · setCurrentTask · createTask · updateTask · deleteTask
Epics & execution
listEpics · getEpic · createEpic · confirmEpicPlan · startEpic · enqueueEpicTask · getEpicExecution · startEpicExecution
Agent jobs & profiles
listAgentProfiles · resolveAgentProfile · enqueueAgentJob · listAgentJobs · getAgentJob · claimNextAgentJob · completeAgentJob · requestDelegation
Context & memory
getTaskContext · getProjectContext · searchContext · addContextFile · appendTaskNote · logActivity
Sync & monitoring
syncJiraTasks · getGithubActivity · getVercelDeployments · checkProjectHealth · getExecutiveSummary · getProjectProposals
Built-in MCP prompts
load-task-context · session-handoff
Example prompts
- Open the ProjectMind MCP docs and summarize authentication options.
- Explain load-task-context and session-handoff MCP prompts.
Prefer read tools first (listTasks, getProjectContext, searchContext). Mutations should follow your confirmation—especially epic execution and agent job enqueue.
Frequently asked questions
- Is ProjectMind preinstalled in ChatGPT or Claude?
- No. Add ProjectMind as a custom MCP connector (or sign in with OAuth when the client supports remote MCP). Use your ProjectMind account and approve project access in the consent flow.
- Will the agent change my project without asking?
- Destructive or high-impact MCP writes—deleting tasks, starting epic execution, completing agent jobs—should run only after you confirm in chat or in the ProjectMind UI. Prefer read tools first (listTasks, getTaskContext, searchContext).
- Which authentication should I use?
- OAuth is best for interactive assistants. Project API keys (imk_…), global keys (imgk_…), and bucket keys (imbk_…) work in headers for headless clients. Never put keys in query strings.
- Can agents run epics and background jobs?
- Yes, when your role allows it. Tools such as confirmEpicPlan, startEpicExecution, and enqueueAgentJob enqueue work your team can monitor in ProjectMind. Pause or cancel from the app if something looks wrong.
- Where is the full MCP reference?
- See /docs/mcp on projectm.dev for endpoint URL, client setup tables, and the complete tool list.