McTime ACTION
Start Clocking
Start a new clocking time entry. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's McTime account once, then configure and run Start Clocking from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "mctime-start-clocking",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
mctime: { authProvisionId: "apn_xxxxxxx" },
userId: "User ID",
dateTime: "Start Datetime",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "mctime-start-clocking",
"configured_props": {
"mctime": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User ID",
"dateTime": "Start Datetime"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "mctime",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "mctime-start-clocking",
arguments: {
userId: "User ID",
dateTime: "Start Datetime",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
userId User ID | string | The ID of the user. If provided clock will be assigned for this user. If not provided clock will be assigned to the user who is authenticated and who is making the API call. Optional Dynamic |
dateTime Start Datetime | string | The dateTime when the clock has started. Provide in ISO-8601 format containing a timezone, eg. 2022-04-25T08:00:00+03:00. Required |
timeType Time Type | string | The type of the clocking time entry Required |
comment Comment | string | A comment for the clocking time entry Optional |
organizationId Organization ID | string | The ID of the organization for the clocking time entry Required Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- mctime-start-clocking
- Version
- 0.0.2
- App
- McTime
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗