Skip to main content
Use MCP when ChatGPT, Codex, or another MCP client should work with Plangrep projects and uploaded chat files. Use the Open API instead when your own application calls Plangrep directly.

​
MCP server URL

Use the production server for live projects: 
https://plangrep.com/api/mcp/v1
Plangrep owns the MCP OAuth facade. MCP clients should not be configured directly against Auth0.

​
Source discovery workflow

Use plangrep_search_project_sources before reading source text or displaying source images. It returns source handles and metadata that the follow-up tools can use. 
plangrep_search_project_sources
plangrep_read_source_text
plangrep_show_source_image
plangrep_show_source_images
plangrep_search_project_sources accepts a mode field:
ModeUse when
semanticYou want vector search over source meaning. This is the default.
grepYou want keyword or boolean prepared-text search.
regexYou need case-insensitive multiline regex search over prepared source text.
autoAn agent should try semantic search first and receive keyword follow-up guidance if vectors are not ready.
For organization-wide project discovery, plangrep_search_projects accepts sourceSearchMode with the same values.

​
Artifact and source handles

MCP clients should not fetch Open API artifact URLs directly. The MCP server converts source and artifact URLs into opaque handles. Pass image handles to plangrep_show_artifact_image or plangrep_show_source_image, and pass source handles to plangrep_read_source_text when you need bounded text.