compose_contract — rolefig MCP Prompt
compose_contract
is one of 2 prompts on the
rolefig
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke compose_contract from your client
- Claude Code rolefig Prompt/compose_contract run in your project directory
- Claude Desktop rolefig Prompt/compose_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor rolefig Prompt/compose_contract ~/.cursor/mcp.json
- VS Code rolefig Prompt/compose_contract .vscode/mcp.json
- Zed rolefig Prompt/compose_contract ~/.config/zed/settings.json
- Windsurf rolefig Prompt/compose_contract ~/.codeium/windsurf/mcp_config.json
- Cline rolefig Prompt/compose_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI rolefig Prompt/compose_contract ~/.gemini/settings.json
- Grok rolefig Prompt/compose_contract .mcp.json (in your project root)
- ChatGPT rolefig Prompt/compose_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai rolefig Prompt/compose_contract Settings → Connectors → Add custom connector
- LangChain rolefig Prompt/compose_contract pip install langchain-mcp-adapters
Other prompts on this server
rolefig also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.