TAKO MCP Server for Okta
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_BASE_URL | No | Base URL for HTTP transport (supports https for reverse proxy) | http://127.0.0.1:8000 |
| TOKEN_METHOD | No | Auth method: API_TOKEN or OAUTH2 | API_TOKEN |
| OKTA_API_TOKEN | No | API token (required if TOKEN_METHOD=API_TOKEN) | |
| ENABLE_AGENT_MODE | No | Enable Agent Mode | false |
| OKTA_CLIENT_ORGURL | Yes | Okta org URL (e.g., https://example.okta.com) | |
| OKTA_MCP_LOG_LEVEL | No | Log level: DEBUG, INFO, WARNING, ERROR | INFO |
| OKTA_OAUTH2_SCOPES | No | OAuth2 scopes | okta.users.read okta.groups.read okta.apps.read |
| OKTA_CONCURRENT_LIMIT | No | Max concurrent API requests | 10 |
| OKTA_OAUTH2_CLIENT_ID | No | OAuth2 client ID (required if TOKEN_METHOD=OAUTH2) | |
| OKTA_OAUTH2_PRIVATE_KEY_PEM | No | Private key in PEM format (required if TOKEN_METHOD=OAUTH2) | |
| OKTA_MCP_EXECUTION_TIMEOUT_SECONDS | No | Code execution timeout | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityInactive
ResponsivenessNo issues