trial-onboarding — Agent Module MCP Prompt
trial-onboarding
is one of 3 prompts on the
Agent Module
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke trial-onboarding from your client
- Claude Code Agent Module Prompt/trial-onboarding run in your project directory
- Claude Desktop Agent Module Prompt/trial-onboarding ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent Module Prompt/trial-onboarding ~/.cursor/mcp.json
- VS Code Agent Module Prompt/trial-onboarding .vscode/mcp.json
- Zed Agent Module Prompt/trial-onboarding ~/.config/zed/settings.json
- Windsurf Agent Module Prompt/trial-onboarding ~/.codeium/windsurf/mcp_config.json
- Cline Agent Module Prompt/trial-onboarding ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent Module Prompt/trial-onboarding ~/.gemini/settings.json
- Grok Agent Module Prompt/trial-onboarding .mcp.json (in your project root)
- ChatGPT Agent Module Prompt/trial-onboarding Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent Module Prompt/trial-onboarding Settings → Connectors → Add custom connector
- LangChain Agent Module Prompt/trial-onboarding pip install langchain-mcp-adapters
Other prompts on this server
Agent Module also offers 3 resources — 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 24 September 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.