pocketbase-mcp

Generate Apple client secret

generate_apple_client_secret

Generate an Apple OAuth2 client secret JWT from Apple developer credentials to enable Apple sign-in. Requires superuser access.

Instructions

Generate a new Apple OAuth2 client secret (JWT) from your Apple developer credentials. Superuser only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clientId": "<clientId>",
      "teamId": "<teamId>",
      "keyId": "<keyId>",
      "privateKey": "<privateKey>",
      "duration": "<duration>"
    },
    "name": "generate_apple_client_secret"
  }
}

Input Schema

Name	Required	Description
`keyId`	Yes	Apple private key id.
`teamId`	Yes	Apple Developer Team ID.
`clientId`	Yes	Apple Services ID (client id).
`duration`	Yes	Secret validity duration in seconds (max ~15777000).
`privateKey`	Yes	Apple private key contents (PEM).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only says it 'generates' a secret and requires superuser, but does not state whether the secret is returned, persisted, rotated, or revoked, nor any security side effects such as logging or expiration of previous secrets. This is a significant gap for a security-sensitive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences with no filler. The action and resource are front-loaded, and the superuser restriction is a valuable qualifier. Every word contributes to the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should clarify what the tool returns and any side effects. It does not explain whether the generated secret is returned in the response, saved somewhere, or if it invalidates existing secrets. For a secret-generating tool, this missing information leaves an agent uncertain about how to use the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all five parameters already meaningfully described. The description adds only high-level context about using 'Apple developer credentials' and does not improve per-parameter understanding, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Generate', the resource 'Apple OAuth2 client secret (JWT)', and the source 'Apple developer credentials'. It distinguishes itself from generic secret tools by specifying OAuth2 and JWT, and no sibling tool has the same function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates a usage constraint ('Superuser only') but does not explicitly say when to use this tool versus alternatives, when not to use it, or what prerequisites are needed beyond credentials. The implied context is clear, but explicit guidance is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server