Temporal MCP Server

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation3/5
Several tools are clearly distinct, but there is notable overlap: fetch_workflow_history largely duplicates get_workflow_execution_history, and list_closed_workflow_executions is a specialized subset of list_workflow_executions. Descriptions help clarify the differences, but an agent could easily pick the wrong tool.
Naming Consistency5/5
Tool names consistently follow a verb_noun pattern using snake_case: get, list, describe, fetch, terminate. The naming is predictable and readable, with only a minor stylistic variation between get and fetch.
Tool Count5/5
With 7 tools, the server is well-scoped for workflow inspection and management. Each tool covers a meaningful operation without unnecessary bloat.
Completeness3/5
The tool set covers workflow observation well: listing, describing, raw history, and step summaries. However, it lacks common lifecycle operations such as starting, signaling, canceling, or querying workflows, and terminate is the only mutation available.
Average 3.6/5 across 7 of 7 tools scored. Lowest: 2.9/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. It states what information is returned, but it does not explicitly say the operation is read-only, describe error behavior, or explain edge cases such as what happens when the workflow does not exist or when no run has occurred.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that efficiently states the tool's purpose and lists useful output fields. The trailing 'and more' adds mild vagueness, but overall the description is concise and appropriately structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the main purpose and some return fields, and the schema fully documents all parameters. However, with no output schema, no annotations, and no distinction from sibling history tools, the description is not fully self-sufficient for an agent trying to choose among the related tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter meanings are already fully documented. The description adds no parameter-specific detail beyond the schema, making the baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'Get detailed information about a workflow execution,' followed by concrete data points like status, history length, start time, and close time. It is clear about what the tool does, though it does not explicitly differentiate itself from the history-focused sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance about when to use this tool versus sibling tools such as get_workflow_execution_history or list_workflow_executions. It also doesn't mention that omitting runId returns the latest run or that region defaults to 'us'—those details are only in the schema, not in usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must carry the full burden of behavioral disclosure. It does mention Temporal visibility query syntax and optional filtering, but it does not state that the operation is read-only, what the return shape is, whether there are pagination implications, or what happens with an invalid query. This is insufficient for a tool with no annotation safety signals.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, front-loaded with the action and resource, and uses two short sentences with no wasted words. Every sentence adds useful information about the tool's behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that there is no output schema, no annotations, and a close sibling 'list_closed_workflow_executions', the description is not complete enough. It fails to clarify whether this tool lists only open, only closed, or all executions, and it does not explain return behavior. An agent could easily pick the wrong tool or miss important listing semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters 'query', 'region', and 'pageSize' are already fully documented with defaults and enums in the schema. The description adds only high-level filter categories and no parameter-specific detail beyond that, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List'), a resource ('workflow executions'), and the key capability of optional filtering using Temporal visibility query syntax. It is clear what the tool does, but it does not distinguish itself from the sibling 'list_closed_workflow_executions', so it stops short of full sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: when you need to list workflow executions and optionally filter by workflow type, status, start time, etc. However, it provides no explicit exclusions or comparison with alternatives such as 'list_closed_workflow_executions', so the guidance remains implicit rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description bears the full burden of behavioral disclosure. It only says this is a convenience method that fetches 'complete workflow history' and is similar to another tool; it does not explain the meaning of 'complete', what is returned, which run is used by default, or any error/edge-case behavior. The schema mentions 'latest run' but the description itself is vague.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is appropriately short and front-loaded: the first clause states the core action, and the second sentence provides routing guidance. The hedge 'may be easier' and the undefined 'workflow handle' add mild ambiguity, but no sentence is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and no return-value description, the agent is left to infer what 'complete workflow history' actually contains. There is also a potential ambiguity between 'complete workflow history' and the schema's fact that only the latest run is fetched when runId is omitted. The description does not resolve this, making it incomplete for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3 even without parameter detail in the description. The description adds little beyond identifying workflowId as the ID-based handle, and its 'workflow handle' wording is somewhat inconsistent with the actual parameter name. The schema already documents runId and region well.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear action and resource: 'fetch complete workflow history' and distinguishes this from get_workflow_execution_history by positioning it as easier 'when you only have the workflow ID.' However, the phrase 'using the workflow handle' introduces an undefined term that the schema calls workflowId, which slightly weakens the otherwise specific purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly names the closest alternative, get_workflow_execution_history, and gives a use-case condition for choosing this tool: 'easier to use when you only have the workflow ID.' It does not state when not to use it or describe exclusion cases, but the guidance is clear enough for routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly discloses that the result is complete and raw, includes all event types, and can be very large, which is valuable context. It does not mention pagination or output format, but the size warning is substantive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core function, followed by a necessary warning and a pointer to an alternative. Every sentence earns its place with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers the core function and points to a clear alternative for compact summaries, but leaves the relationship with the fetch_workflow_history sibling unexplained and provides no return-format or pagination hints. For a tool with no annotations and no output schema, this is a moderate gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all three parameters including the region enum. The description adds no additional parameter-level details, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: get the complete RAW execution history of a Temporal workflow, listing event types such as activity executions, signals, and timers. However, the sibling 'fetch_workflow_history' appears nearly identical and is not differentiated, so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes to get_workflow_step_results for a compact summary with resultUri, and warns about the large size of the response. Does not address when to choose this over the similarly named fetch_workflow_history sibling, so the guidance is not fully exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It usefully explains that closed means completed, failed, terminated, etc., but it does not mention ordering, pagination results, region defaulting, or any rate/safety considerations. A borderline adequate disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence, front-loaded with the core action, and the parenthetical status list is compact and informative. There is no wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The combination of schema and description is sufficient for a basic invocation: required times are clear, defaults are in the schema, and the resource type is named. However, there is no output schema and the description does not describe return shape, paging behavior, or when to prefer this over list_workflow_executions, leaving meaningful gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema covers all four parameters with descriptions, formats, defaults, and enums (100% coverage), so the description does not need to explain parameter semantics. It adds no param-specific detail beyond the time range, matching the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List'), a specific resource ('workflow executions'), and a clear qualifier ('closed – completed, failed, terminated, etc'), which differentiates it from sibling list_workflow_executions. The time-range constraint is also stated clearly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description makes the intended context clear: use when you need executions that have already closed within a specified time range. It does not explicitly name alternatives or exclusions, but the state filter and time range are enough context to guide selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose that termination is immediate and that the workflow is marked as terminated. However, it does not mention irreversibility, required permissions, or side effects, which would be valuable for a mutating tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences with no filler. The action and primary consequence are front-loaded, and every word contributes to understanding the tool's behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple termination action with fully documented parameters, the description is mostly adequate. However, with no annotations and no output schema, it could be more complete by noting that termination is irreversible and that only running executions are affected.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already fully documents all four parameters. The description adds no parameter-level meaning beyond that, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Terminate') and resource ('running workflow execution'), and adds the key consequence: it stops immediately and marks the execution as terminated. This clearly differentiates the tool from its read-only siblings (list/get/describe/fetch history).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'running workflow execution' gives clear context for when to use this tool. It does not explicitly name alternatives or exclusion cases, but none of the sibling tools perform termination, so the usage intent is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It clearly conveys that the tool returns a processed, compact summary rather than raw history, and that it exposes resultUri for further log downloads. It does not discuss errors, pagination, or permissions, but these are minimal for a read-only getter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each earning its place: what it does, why it is useful, and a concrete use case. No filler or repetition beyond the intentional emphasis on resultUri.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, but the description lists the key return elements (resultUri, step names, durations, success status) and clearly situates the tool among history-focused siblings. It is sufficient for an agent to select and call the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already well-documented. The description adds no additional meaning about how workflowId, runId, or region interact with the output, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Get') and resource ('processed step results from a workflow execution'), and lists concrete output fields (resultUri, step names, durations, success status). It also distinguishes itself from history tools by emphasizing it is a 'compact summary' rather than the 'full raw history'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context for when to use the tool: for analyzing step outcomes and for retrieving resultUri to download logs. It implies a contrast with full-history alternatives but does not explicitly name sibling tools or state when not to use them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![temporal-mcp MCP server](https://glama.ai/mcp/servers/shimantakb-sprinto/temporal-mcp/badges/card.svg)](https://glama.ai/mcp/servers/shimantakb-sprinto/temporal-mcp)

Score Badge

Copy to your README.md:

[![temporal-mcp MCP server](https://glama.ai/mcp/servers/shimantakb-sprinto/temporal-mcp/badges/score.svg)](https://glama.ai/mcp/servers/shimantakb-sprinto/temporal-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shimantakb-sprinto/temporal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server