invokeKnowledgeAgent
Broad workspace questions requiring reasoning across multiple Devplan sources
LABSCO SUMMARY
Naming the tools so you can steer the agent, while admitting the list is partial, is the right kind of documentation honesty.
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.
What it is
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.
What you get
- 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
Requirements
OAuth, or a bearer API key beginning dpsk-, scope mcp.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Asking a question that spans the workspace
Let the knowledge agent reason across signals, notes and projects rather than searching each.
02
Finding a specific piece of evidence
Search entities directly when you know what you are looking for.
03
Planning a feature
Start the planning run and poll it rather than holding a conversation open.
04
Grounding a plan in the codebase
Read the repository descriptions and code research already in the workspace.
8 tools
Listed in project docs. Your client may show a different list.
search_devplan_entities
Focused semantic search across signals, insights, changes, call notes, projects, feature catalog, repo descriptions, research
list_product_feature_catalog
Product areas and feature IDs/names
list_workspace_projects
Project summaries, status, owners, assignees, linked planning docs
list_repository_descriptions
Repo summaries from Devplan code research
list_code_research
Code research artifacts in the workspace
start_feature_planning
Start a feature planning run
check_feature_planning_status
Check status of a feature planning run
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth or Bearer dpsk- API key; scope mcp
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://app.devplan.com/api/v1/mcpRequirements
- OAuth or Bearer dpsk- API key; scope mcp
