Project MCP

Every project on Agentics Fabrik has its own MCP server, mounted at the project's URL. Add it to your assistant and the assistant is scoped to that one project — read its vision, list its solution records, and archive the conversation you just had, all without ever naming the project again.

https://agentics.dk/p/{owner}/{project}/mcp

Replace {owner} and {project} with the project's path — e.g. https://agentics.dk/p/pksorensen/agentic-live/mcp.

How it works

The project is the mount path. No tool takes a project argument, so picking the wrong project is structurally impossible rather than merely discouraged. Every result echoes { "project", "owner" } so the model can catch it if your intent drifted.

Auth is lazy, the same posture as the Platform MCP:

1. Add it anonymously. initialize, tools/list, and the resource list all work with no credentials, so any client can add the connector and inspect it.
2. Sign in to call a tool. The first tools/call returns a 401 pointing at this project's OAuth protected-resource metadata; your client runs the sign-in flow against Agentics' Keycloak.
3. Access is checked per project. A signed-in caller without access to this project gets a 403 — being signed in is not the same as being invited.
4. Writes are owner-gated. Read tools are open to anyone with project access; update_vision requires you to be the project owner.

Add it to your client

• Claude (Desktop / claude.ai): Settings → Connectors → Add custom connector → paste the project's URL above. Claude registers automatically (CIMD) and opens the sign-in step when a tool needs it.

• ChatGPT: Settings → Connectors → add the URL as a custom MCP connector.

• Claude Code:

  claude mcp add --transport http my-project https://agentics.dk/p/{owner}/{project}/mcp
  

  Copy

• Any MCP client: use the Streamable HTTP transport with the URL above.

What you get

Tool	What it does
whoami	Who you are on this project and your role (owner or contributor).
project_info	The project's name, description, and key URLs (page, solution, external chats, vision resource).
get_vision	Read the project's vision document (Markdown).
update_vision	Owner only. Replace the full vision document — must include the headings Vision, Goals, Non-Goals, Target Users, Success Criteria. Committed to the project repo.
list_solution_records	User stories, roles, acceptance-criteria count, and ADRs.
archive_chat	Save the current conversation to the project as an External Chat (Solution → Chat → External Chats).

The vision document is also exposed as an MCP resource for clients that support resources:

agentics-project://{owner}/{project}/vision

The one-line shortcut: prompt.md

You don't have to explain the project to your assistant. Paste this into any agent that can fetch a URL:

Fetch https://agentics.dk/p/{owner}/{project}/prompt.md

One call gets it the whole briefing: what the project is (description plus a summary of the live vision document), the MCP URL, the claude mcp add command, the full tool table, and the vision resource URI. The document is generated from the same source as the server, so it never drifts from the tools it describes.

Public projects serve prompt.md anonymously — share the line with anyone. A private project requires an authenticated caller with access; to everyone else it simply 404s, so its existence stays hidden.

Want the platform as a whole rather than one project? Use the Platform MCP. Looking for a person? Every member also has a Personal MCP.