FreeAgent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREEAGENT_CLIENT_ID | Yes | Your FreeAgent client ID from the Developer Dashboard | |
| FREEAGENT_ACCESS_TOKEN | Yes | Your FreeAgent OAuth access token | |
| FREEAGENT_CLIENT_SECRET | Yes | Your FreeAgent client secret from the Developer Dashboard | |
| FREEAGENT_REFRESH_TOKEN | Yes | Your FreeAgent OAuth refresh token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_timeslipsC | List timeslips with optional filtering |
| get_timeslipC | Get a single timeslip by ID |
| create_timeslipC | Create a new timeslip |
| update_timeslipC | Update an existing timeslip |
| delete_timeslipC | Delete a timeslip |
| start_timerC | Start a timer for a timeslip |
| stop_timerC | Stop a running timer for a timeslip |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no ambiguity. The tools cover specific actions (create, delete, get, list, start timer, stop timer, update) on the 'timeslip' resource, making it easy for an agent to select the correct tool for any required operation without confusion.
All tool names follow a consistent verb_noun pattern (e.g., create_timeslip, delete_timeslip). The naming is uniform across all tools, using snake_case and clear action verbs, which enhances predictability and readability for agents.
With 7 tools, the count is well-scoped for managing timeslips, covering essential CRUD operations and timer functionality. Each tool serves a distinct and necessary role, making the set neither too sparse nor overloaded for the domain.
The tool set provides complete coverage for the timeslip domain, including full CRUD operations (create, get, list, update, delete) and additional lifecycle features (start and stop timer). There are no obvious gaps, ensuring agents can handle all expected workflows without dead ends.