A Model Context Protocol (MCP) server for Apptio Target Process
A Model Context Protocol (MCP) server for Apptio Target Process
The Model Context Protocol (MCP) is a standard that enables AI assistants to interact with external tools and services through a unified interface. MCP servers provide these capabilities by exposing tools and resources that AI assistants can use to accomplish tasks.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| search_entities | Search for Targetprocess entities (UserStory, Bug, Task, Feature) with filtering and includes. json { "type": "UserStory", // Required: Entity type to search for "where": "EntityState.Name eq 'Open'", // Optional: Filter |
| get_entity | Get detailed information about a specific entity. json { "type": "UserStory", // Required: Entity type "id": 123456, // Required: Entity ID "include": ["Project", "Team"] // Optional: Related data to include } |
| create_entity | Create a new entity in Targetprocess. json { "type": "UserStory", // Required: Entity type to create "name": "Story Name", // Required: Entity name "description": "Details...", // Optional: Entity description "project": |
| update_entity | Update an existing entity. json { "type": "UserStory", // Required: Entity type "id": 123456, // Required: Entity ID "fields": { // Required: Fields to update "name": "New Name", "description": "New description", "status |
| inspect_object | Inspect Targetprocess objects and properties through the API. json { "action": "list_types", // Required: Action to perform "entityType": "UserStory", // Required for some actions: Entity type to inspect "propertyName": |
{
"mcpServers": {
"targetprocess": {
"command": "./scripts/run-local.sh",
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.