Local Infusion · OAuth Scopes

Local Infusion OAuth Scopes

OAuth 2.0 derived

Local Infusion publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Local Infusion API on a user’s behalf.

Tokens are issued from https://mylocalinfusion.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyHealthcareHealth ServicesInfusion TherapySpecialty PharmacyAmbulatory CarePatient ServicesAutoimmuneChronic CareMCPWordPress

Scopes: 1 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://mylocalinfusion.com/oauth/authorize

Token URL
https://mylocalinfusion.com/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Access the site's Model Context Protocol server.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-25'
method: derived
source: openapi/local-infusion-mcp-api-openapi.yml, openapi/local-infusion-oembed-1-0-api-openapi.yml,
  openapi/local-infusion-root-api-openapi.yml, openapi/local-infusion-wp-abilities-v1-api-openapi.yml,
  openapi/local-infusion-wp-v2-api-openapi.yml
schemes:
- name: mcpOAuth2
  source: openapi/local-infusion-mcp-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
- name: mcpOAuth2
  source: openapi/local-infusion-oembed-1-0-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
- name: mcpOAuth2
  source: openapi/local-infusion-root-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
- name: mcpOAuth2
  source: openapi/local-infusion-wp-abilities-v1-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
- name: mcpOAuth2
  source: openapi/local-infusion-wp-v2-api-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mylocalinfusion.com/oauth/authorize
    tokenUrl: https://mylocalinfusion.com/oauth/token
  description: OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC
    8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-server (fetched
    2026-08-25, HTTP 200). Guards the `mcp` namespace; the RFC 9728 protected-resource metadata
    names https://mylocalinfusion.com/wp-json/mcp/mcp-oauth-server.
scopes:
- scope: mcp
  description: Access the site's Model Context Protocol server.
  flows:
  - authorizationCode
  sources:
  - openapi/local-infusion-mcp-api-openapi.yml
  - openapi/local-infusion-oembed-1-0-api-openapi.yml
  - openapi/local-infusion-root-api-openapi.yml
  - openapi/local-infusion-wp-abilities-v1-api-openapi.yml
  - openapi/local-infusion-wp-v2-api-openapi.yml

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/local-infusion-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.