MCP Beyond Tools

Tools are most of the MCP surface, but not all of it. Your agent can also read resources on demand, pick up prompts as slash commands, and open a CRM board in clients that render MCP apps.

Resources

Resources are read-only content addressed by URI:

URI family	Contains
`cofounder://company`	The company's current state
`cofounder://billing`	Billing status
`cofounder://library/`	Library files, browsable by path
`cofounder://outputs/`	Generated artifacts by id
`skill://{name}/SKILL.md`	Cofounder's own operating guides

The skills are the same playbooks the Cofounder plugins ship — how to onboard a company, run setup, work the repo — so your agent can read skill://cofounder-onboard/SKILL.md instead of guessing the sequence.

Everything here is also reachable as plain tools (skills_list, skills_get, library_*), so clients without resource support don't miss anything.

Prompts

Prompts register as slash commands in clients that support them (/mcp__cofounder__<name>). Each one packages a canned instruction for a common job — generate-image and generate-video for the media pipeline, for example.

The CRM app

crm_board_open renders the company's CRM as a read-only board inside clients that support MCP apps, so you can browse deals, accounts, and contacts without leaving the agent. The same data is callable as plain crm_* tools, so nothing is lost on other clients.

What MCP adds

The same operations come back a little richer on MCP. media_generate and media_get (cofounder media generate / media get on the CLI) return resource links to the finished assets under cofounder://outputs/, so your agent can chain straight into reading or posting them. And tools that are really resource reads (skills_*, library_*) also surface as resources, so clients with native support can browse them without spending a tool call.

Next steps

The Reference names every operation across all three surfaces and shows how the spellings map.