Home MCP Connectivity Connecting Timether to AI tools with the MCP Server

Connecting Timether to AI tools with the MCP Server

Last updated on Jun 19, 2026

Timether provides a hosted MCP server that lets compatible AI tools connect to your Timether workspace securely.

MCP stands for Model Context Protocol. It is a standard way for AI tools and assistants to access approved data and actions from connected apps.

With Timether MCP, supported AI tools can help you work with workspace data such as projects, clients, time entries, timesheets, invoices, expenses, members, and reports, depending on your role and granted permissions.

Timether MCP server URL

The hosted Timether MCP server is available at:

https://api.timether.com/mcp

This is the endpoint MCP-compatible clients use when connecting to Timether.

Plan requirements

Timether MCP access is available to active workspaces on:

  • Team

  • Business

The workspace must include the public_api_access entitlement.

MCP access is not available on Free or Solo Pro workspaces.

If your workspace does not support public API access, MCP clients will not be able to connect.

How MCP authorization works

Timether MCP uses a secure OAuth authorization-code flow.

When an MCP client connects to Timether, you will be sent to Timether in your browser to sign in and approve access.

Login and consent are handled through:

https://app.timether.com

During consent, you select one eligible workspace.

After approval, the connection is bound to that selected workspace. This means the MCP client can only access the workspace you approved.

Workspace-bound access

MCP connections are scoped to a single workspace.

If you belong to multiple workspaces, the MCP client does not automatically receive access to all of them. You choose one workspace during the consent step, and the issued tokens are tied to that workspace.

This helps keep workspace data separated and prevents accidental access to the wrong workspace.

For example, if you approve access to your agency workspace, the MCP client cannot use that same connection to access your personal workspace.

Supported access scopes

Timether MCP supports the following OAuth scopes:

  • timether:read

  • timether:write

  • timether:admin

The scope controls what level of access the MCP client can request.

A read-only connection can retrieve information.

A write-enabled connection can perform supported changes.

Admin-level access is reserved for higher-permission operations and may depend on your workspace role.

What data and tools are available

Timether MCP exposes explicit tools for approved workspace actions.

Depending on your role, plan, billing state, and granted scopes, an MCP client may be able to work with areas such as:

  • Workspace context

  • Members and invites

  • Clients

  • Projects

  • Tags

  • Timers

  • Time entries

  • Timesheets

  • Expenses

  • Invoices

  • Settings

  • Email preferences

  • Notifications

  • Audit logs

  • Data portability

Available tools may differ depending on the connected user’s permissions.

What is not exposed through MCP

For safety, some sensitive operations are not available through MCP tools.

Timether does not expose MCP tools for:

  • Authentication bootstrap

  • API token management

  • Zapier connection flows

  • Browser extension connection flows

  • Integration events

  • Webhook subscriptions

  • Payment-provider credentials

These areas must be managed through the Timether app or the relevant integration flow.

How Timether keeps MCP access safe

Timether filters MCP tools based on several checks.

Tool access can depend on:

  • OAuth scope

  • Workspace role

  • Plan entitlement

  • Billing state

  • Current workspace capabilities

This means an MCP client only receives access to actions that are allowed for the connected user and workspace.

If your role or workspace plan does not allow a certain action, the tool will not be available or the request will be rejected.

Managing MCP connections

You can review and revoke OAuth connections from:

Account → Integrations

If you no longer use an AI tool or want to remove its access, revoke the connection from this page.

Once revoked, the client will no longer be able to use that Timether connection.

When access may stop working

An MCP connection may stop working if:

  • The connection is revoked

  • The workspace is downgraded

  • The workspace no longer has public_api_access

  • Your membership becomes inactive

  • Your account is disabled

  • The workspace is no longer active

  • The MCP feature is disabled

If access stops unexpectedly, check your workspace plan, account status, and integrations page.