# Okta MCP Server MCP Server for the Okta API, enabling Claude to interact with Okta organizations. ## Demo  ## Tools 1.
## Tools 1. okta_list_users_make_request - List users in the Okta organization - Optional inputs: -. Exposed over MCP by the okta mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Returns — List of users with their basic informationTroubleshooting — If you encounter permission errors, verify that: 1. Your API token is valid 2. The API token has sufficient permissions for the operations you'reYou will need 2 environment variables: OKTA_DOMAIN, API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Okta's toolset — Returns, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by YiyangLi; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Returns | List of users with their basic information |
| Troubleshooting | If you encounter permission errors, verify that: 1. Your API token is valid 2. The API token has sufficient permissions for the operations you're trying to perform 3. The Okta domain is correctly specified |
{
"mcpServers": {
"okta": {
"command": "npx",
"args": [
"-y",
"@yiyang.1i/okta-mcp-server"
],
"env": {
"OKTA_DOMAIN": "your-domain.okta.com",
"API_TOKEN": "your-api-token"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OKTA_DOMAIN | Configuration value read at startup. | Optional |
| API_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.