Does Codex support the Wakatime MCP server?

Yes. Codex connects to the Wakatime MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

Do I need an API key to connect Wakatime to Codex?

No. You sign in to Wakatime once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.

Which Wakatime tools can Codex use?

All 20 Wakatime tools your team allows, such as List Projects, Get Project Commits, Delete Heartbeat. Admins can narrow that list per team.

Can I control which teammates use Wakatime in Codex?

Yes. Role-based access control decides who can use Wakatime and which of its tools appear in Codex, and every call is logged with the person's identity.

What if Codex doesn't show Wakatime tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Wakatime to Codex (MCP setup guide)

Ask Codex to use the list projects tool in Wakatime
Ask Codex to use the get project commits tool in Wakatime
Ask Codex to use the delete heartbeat tool in Wakatime
Ask Codex to use the get user profile tool in Wakatime
Ask Codex to use the get heartbeats tool in Wakatime

1. Enable Wakatime in Metorial
In your Metorial portal, enable the Wakatime MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Wakatime tools.

Once Wakatime is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

List Projects: List all coding projects that have recorded activity.
Get Project Commits: Retrieve commit history for a specific project with time-spent-coding data per commit.
Delete Heartbeat: Delete a specific heartbeat by its ID.
Get User Profile: Retrieve the current user's profile information including display name, email, timezone, last active plugin, social profiles, plan details, and machines.
Get Heartbeats: Retrieve raw coding activity events (heartbeats) for a specific day.
Get Private Leaderboards: List all private leaderboards the user has access to.
Create External Duration: Record activity durations from sources other than IDE plugins, such as calendar events, meetings, or code reviews.
Get Durations: Retrieve coding activity for a given day as time duration blocks.
Get Coding Stats: Retrieve aggregated coding statistics for a configurable time range.
Get Leaderboard: Access public or private leaderboards of users ranked by coding activity.
Get Machines: List all machines (computers) that have sent coding activity, including hostname, IP, and last seen time.
Get Coding Summaries: Retrieve coding activity summaries for a given date range, segmented by day.
Get Insights: Access deeper analytics about coding activity for a given time range.
Manage Data Exports: List existing data exports or request a new full data export of all coding activity.
Get Goals: Retrieve all coding goals.
And 5 more on the Wakatime MCP server page.

Limit which Wakatime tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Wakatime tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Wakatime to AI agents with Metorial.

Does Codex support the Wakatime MCP server?
Yes. Codex connects to the Wakatime MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Wakatime to Codex?
No. You sign in to Wakatime once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Wakatime tools can Codex use?
All 20 Wakatime tools your team allows, such as List Projects, Get Project Commits, Delete Heartbeat. Admins can narrow that list per team.
Can I control which teammates use Wakatime in Codex?
Yes. Role-based access control decides who can use Wakatime and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Wakatime tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.