Most vendors either publish a frozen catalogue that rots or publish nothing. Devplan says: here are the names you will see, use them to check the agent is doing what you meant. That is a genuinely useful middle position. On the product side, the pairing of a broad knowledge agent with a focused entity search is the standard shape, and code research being a first-class source is the part that distinguishes this from a generic wiki search.
Devplan's endpoint over their product-planning workspace. Their documentation names eight common tools and says explicitly that the list is not exhaustive, offered so you can steer the agent rather than as a specification.
- invokeKnowledgeAgent — broad questions that need reasoning across several Devplan sources at once
- search_devplan_entities — focused semantic search over signals, insights, changes, call notes, projects and the feature catalogue
- list_product_feature_catalog, list_workspace_projects — the product areas and the projects with owners and status
- list_repository_descriptions and list_code_research — what Devplan's code research has established about the repos
- start_feature_planning and check_feature_planning_status — kick off a planning run and poll it
OAuth, or a bearer API key beginning dpsk-, scope mcp.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen