Connect TimeSentry through the MCP server

What MCP provides

TimeSentry's Model Context Protocol server exposes approved tools for time entries, bulk actions, projects, clients, and tasks. Managed agents can also receive assigned custom tools. Each tool call is authenticated and evaluated in TimeSentry's company model.

Choose an authentication method

Hosted MCP clients: use the TimeSentry hosted MCP endpoint and complete its browser-based authorization when supported by the client.
Local stdio clients: configure the TimeSentry MCP package with a company-scoped tsk_ key in the TIMESENTRY_API_KEY secret or environment setting.

Follow the setup fields and transport supported by your AI client. Use the production TimeSentry base URL unless your administrator explicitly provides another environment.

Test safely

Begin with a read-only request, such as listing projects or recent entries. Confirm that the returned company and records are correct. Then test a low-impact create or update in an approved project.

Protect access

Do not paste a tsk_ key into the chat conversation. Store it in the client's secret configuration. Use one key per client or environment, review its last-used date, and revoke it when the client is retired.

Troubleshoot

Confirm the MCP transport, endpoint or package configuration, key status, active company scope, and client authorization. A valid key for the wrong company can return valid but unexpected data.