Articles in this section
Category / Section

Understanding MCP Tool Execution History

5 mins read
Updated:

The MCP Tool Execution History page provides comprehensive monitoring and analytics for all tool executions on your FlowMattic MCP server. This interface allows you to track performance, debug issues, and analyze usage patterns of your MCP tools.

Overview

The execution history page serves as your monitoring dashboard, recording every interaction between MCP clients (like Claude Desktop, VS Code, etc.) and your FlowMattic MCP server. It provides detailed insights into tool performance, success rates, and usage patterns.

MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.10.26 AM.png

Accessing Execution History

You can access the execution history in two ways:

  1. Server-wide History: From the main MCP Server admin page, click the “History” button to view all tool executions across the server
  2. Tool-specific History: From any tool’s dropdown menu, select “Tool History” to view executions for that specific tool only

Page Header

Navigation Elements

Page Title: Shows either “MCP Server Execution History” for all tools or “[Tool Name] - Execution History” for specific tools

Export Button: Downloads execution data in CSV or JSON format for external analysis

Back to Server Button: Returns you to the main MCP Server admin page

Server Information Card

The server info card displays:

  • Server Name: The name of your MCP server
  • Tool-specific Info (when viewing single tool): Shows the specific tool name and its execution method (PHP Function, Workflow, API Endpoint, etc.)

Filtering and Controls

Filter Options

Items per Page: Control how many execution records to display

  • Options: 10, 25, 50, or 100 executions per page
  • Useful for managing large execution logs

Date Range Filter: Narrow down executions by time period

  • All Time: Shows all recorded executions
  • Today: Shows only today’s executions
  • This Week: Shows executions from the current week
  • This Month: Shows executions from the current month

Refresh Button: Manually reload the execution history to see the latest data

MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.11.48 AM.png

Execution History Table

The main table displays execution records with the following columns:

Tool Column

  • Tool Name: The display name of the executed tool
  • Tool ID: The unique identifier used internally (shown in smaller text)

Status Column

  • Success: Green indicator with checkmark icon for successful executions
  • Error: Red indicator with X icon for failed executions

Executed At Column

  • Timestamp: Shows the exact date and time when the tool was executed
  • Format: Displays in your local time format

Execution Time Column

  • Duration: Shows how long the tool took to execute (in seconds)
  • Format: Displayed with 3 decimal places for precision (e.g., “0.002s”)

Client Column

  • Client Type: Shows which MCP client was used to execute the tool
  • Common Types: Claude, OpenAI, Node MCP Client, etc.
  • Badge Format: Displayed as a small badge for easy identification

Actions Column

  • View Details Button: Opens the detailed execution modal with comprehensive information

MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.10.26 AM.png

Execution Details Modal

Clicking “View Details” opens a comprehensive modal with detailed information about the specific execution.

MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.16.03 AM.png

Execution Information Section

  • Tool Name: The executed tool’s display name
  • Execution ID: Unique identifier for this specific execution
  • Status: Success or error indicator
  • Executed At: Precise timestamp of execution

Client Information Section

  • Client Type: The MCP client that initiated the execution
  • User Agent: Technical details about the client software
  • IP Address: The IP address from which the execution was initiated
  • Execution Time: Precise execution duration

Arguments Section

  • JSON Format: Shows the exact parameters passed by the MCP client
  • Copy Button: Allows copying the arguments for debugging or testing
  • Formatted Display: Pretty-printed JSON for easy reading

Results Section

  • JSON Format: Shows the complete response returned to the MCP client
  • Copy Button: Allows copying the results for analysis
  • Includes: Both successful results and error messages when applicable

Pagination Controls

When there are multiple pages of execution history:

Information Display

  • Results Summary: Shows “Showing X to Y of Z items” to indicate current view
  • Current Position: Clearly indicates which results you’re viewing

Navigation Controls

  • Previous/Next Buttons: Navigate between adjacent pages
  • Page Numbers: Direct links to specific pages
  • Ellipsis Indicators: Show when there are many pages available

Export Functionality

Export Modal

The export feature allows you to download execution history for external analysis:

Export Format Options:

  • CSV: Comma-separated values for spreadsheet applications
  • JSON: JavaScript Object Notation for programmatic analysis

Date Range Selection:

  • Start Date: Optional beginning date for the export
  • End Date: Optional ending date for the export
  • Empty Dates: Exports all available data

Limitations:

  • Limited to 10,000 most recent executions
  • Includes all execution details and metadata

MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.16.50 AM.png

Understanding Execution Data

Success vs Error Analysis

  • Success Rate: Monitor the percentage of successful tool executions
  • Error Patterns: Identify tools that frequently fail
  • Performance Trends: Track execution times over time

Client Usage Patterns

  • Popular Clients: See which MCP clients are used most frequently
  • Client-specific Issues: Identify if certain clients have higher error rates
  • Usage Distribution: Understand how different clients interact with your tools

Performance Monitoring

  • Execution Times: Identify slow-performing tools
  • Peak Usage: Understand when tools are used most heavily
  • Resource Usage: Monitor server load patterns

Empty State

When no execution history is available, the page displays:

  • Empty State Message: “No Execution History”
  • Explanation: Indicates that executions will appear once tools are called
  • Next Steps: Guidance on using tools through MCP clients

Troubleshooting with Execution History

Debugging Failed Executions

  1. Check Error Messages: View detailed error information in the execution details
  2. Examine Arguments: Verify that correct parameters were passed
  3. Review Timing: Check if timeouts or performance issues occurred

Performance Analysis

  1. Identify Slow Tools: Look for executions with high execution times
  2. Usage Patterns: Understand peak usage periods
  3. Client Behavior: Analyze how different clients use your tools

Security Monitoring

  1. IP Address Tracking: Monitor where executions originate
  2. Usage Frequency: Identify unusual activity patterns
  3. Client Analysis: Verify expected client types are being used

Best Practices

Regular Monitoring

  • Weekly Reviews: Check execution success rates and performance
  • Error Analysis: Investigate any failed executions promptly
  • Performance Trends: Monitor for degradation in execution times

Data Management

  • Regular Exports: Backup execution history for long-term analysis
  • Archive Old Data: Export and clean up old execution records periodically
  • Documentation: Keep notes on significant execution patterns or issues

Security Practices

  • Monitor Access: Review client types and IP addresses regularly
  • Unusual Activity: Investigate unexpected execution patterns
  • Rate Limiting: Consider implementing rate limits for heavily used tools

Related Features

Integration with Main Admin

  • Tool Cards: Execution counts displayed on main admin tool cards
  • Quick Access: Direct links from tool management to execution history
  • Status Indicators: Real-time status updates based on recent executions

Performance Insights

  • Execution Counts: Track total number of tool uses
  • Success Rates: Monitor reliability of individual tools
  • Usage Analytics: Understand which tools are most valuable

Next Steps

After reviewing execution history:

  1. Optimize Performance: Improve slow-executing tools based on timing data
  2. Fix Errors: Address tools with high failure rates
  3. Scale Resources: Plan server capacity based on usage patterns
  4. Enhance Security: Implement additional monitoring based on access patterns

Related Resources

The execution history page is an essential tool for maintaining and optimizing your MCP server, providing the insights needed to ensure reliable, high-performance tool operations for your AI assistant integrations.

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Access denied
Access denied