Skip to main content

MCP Authentication

Verification Needed

MCP authentication details are pending.

Authentication for the eCourtDate MCP server will likely use the same API credentials (client_id / client_secret) as the REST API. This means the existing eCourtDate API credentials to authenticate MCP connections.

Anticipated Authentication Flow​

  1. Obtain the client_id and client_secret from the eCourtDate Console.
  2. Configure the MCP client with these credentials.
  3. The MCP server validates the credentials and establishes an authenticated session.

Relationship to REST API Authentication​

The MCP server is expected to share the same authentication system as the eCourtDate REST API. For details on how API authentication currently works, see Authentication.

Security Considerations​

  • Store the client_id and client_secret securely. Do not commit them to version control.
  • Use environment variables or a secrets manager to provide credentials to the MCP client.
  • Rotate credentials periodically according to the organization's security policies.

Next Steps​