Schema | NinjaOne MCP

NinjaOne MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`NINJA_SCOPE`	No	OAuth scope	monitoring management control
`NINJA_BASE_URL`	Yes	Your region's host, e.g. https://app.ninjarmm.com (US), https://eu.ninjarmm.com (EU)
`NINJA_CLIENT_ID`	Yes	OAuth client ID
`NINJA_SESSION_KEY`	No	NinjaOne web session cookie value (alternative for writes, expires with browser session)
`NINJA_CLIENT_SECRET`	Yes	OAuth client secret
`NINJA_REFRESH_TOKEN`	No	User-context refresh token (preferred for writes)
`NINJA_LOCAL_AUTH_PORT`	No	Port for the one-time interactive login	3846
`NINJA_DEFAULT_CLIENT_ID`	No	Default org ID for create_ticket

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
search_ticketsA	List tickets from a NinjaOne board. Requires boardId (default: 1). Supports pagination via cursor.
get_ticketA	Get a single NinjaOne ticket by ID.
create_ticketB	Create a new NinjaOne ticket. Requires write auth (refresh token or session key).
update_ticketC	Update an existing NinjaOne ticket. Requires write auth (refresh token or session key).
add_commentA	Add a comment to a NinjaOne ticket. Requires write auth (refresh token or session key).
list_boardsA	Returns known NinjaOne board IDs. NinjaOne has no boards listing API.
list_statusesA	List all NinjaOne ticket statuses with IDs.
list_organizationsC	List NinjaOne organizations (clients).
list_techniciansA	List NinjaOne app users (technicians) with their numeric IDs. Use to look up user IDs for ticket assignment.
get_auth_urlA	Generate a NinjaOne OAuth authorization URL. Open it in a browser to log in as yourself. After authorizing, copy the 'code' parameter from the redirect URL and pass it to exchange_code.
exchange_codeA	Exchange a NinjaOne authorization code for a refresh token. Paste the code from the redirect URL after using get_auth_url. Save the returned refresh_token as NINJA_REFRESH_TOKEN in your MCP client config.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cyberkoder/ninjaone-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server