### Install OpenMCP Server Locally for Cursor Projects

Source: https://www.open-mcp.org/servers/using-a-server

This command installs an OpenMCP server locally and configures it for Cursor projects. Run it from your project root or home directory (`~`) to apply it to all Cursor projects. Replace `{server-id}` with the desired server.

```bash
npx @open-mcp/config add {server-id} \
  .cursor/mcp.json \
  --ENV_VAR=abc123
```

--------------------------------

### Local Server Environment Variables Setup Placeholder

Source: https://www.open-mcp.org/servers/epa-lew

This snippet indicates that no specific environment variables are required for the local installation of this particular server, serving as a general placeholder for environment setup instructions.

```Shell
# No environment variables required for this server
```

--------------------------------

### API: Post Installation Resources

Source: https://www.open-mcp.org/servers/vercel

Documents the 'post_v1_installations_integrationconfigurationid_resources_resou' API endpoint, detailing its required environment variables and input parameters for posting installation resources.

```APIDOC
Endpoint: post_v1_installations_integrationconfigurationid_resources_resou
Environment Variables:
  - API_KEY
Input Schema:
  - integrationConfigurationId (string)
  - resourceId (string)
  - items (array)
```

--------------------------------

### Install OpenMCP Server Locally to Custom Path

Source: https://www.open-mcp.org/servers/using-a-server

This general command allows installing an OpenMCP server locally to a specified configuration file path. Replace `{server-id}` with the desired server and `/path/to/config.json` with your target configuration file.

```bash
npx @open-mcp/config add {server-id} \
  /path/to/config.json \
  --ENV_VAR=abc123
```

--------------------------------

### Install OpenMCP Server Locally for Claude Desktop

Source: https://www.open-mcp.org/servers/using-a-server

Use this command to install an OpenMCP server locally and configure it for Claude Desktop. The command adds the server configuration to the specified Claude desktop configuration file, allowing for local execution. Replace `{server-id}` with the desired server and adjust the path to your Claude config.

```bash
npx @open-mcp/config add {server-id} \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --ENV_VAR=abc123
```

--------------------------------

### API: Head Installation Resources

Source: https://www.open-mcp.org/servers/vercel

Documents the 'head_v1_installations_integrationconfigurationid_resources_resou' API endpoint, detailing its required environment variables and input parameters for checking installation resources.

```APIDOC
Endpoint: head_v1_installations_integrationconfigurationid_resources_resou
Environment Variables:
  - API_KEY
Input Schema:
  - integrationConfigurationId (string)
  - resourceId (string)
```

--------------------------------

### API: Put Installation Resources

Source: https://www.open-mcp.org/servers/vercel

Documents the 'put_v1_installations_integrationconfigurationid_resources_resour' API endpoint, detailing its required environment variables and input parameters for putting installation resources.

```APIDOC
Endpoint: put_v1_installations_integrationconfigurationid_resources_resour
Environment Variables:
  - API_KEY
Input Schema:
  - integrationConfigurationId (string)
  - resourceId (string)
  - data (object)
```

--------------------------------

### Install Figma Server Locally for Claude Desktop

Source: https://www.open-mcp.org/servers/figma

Use the OpenMCP config CLI to add the Figma server to your Claude desktop client configuration. This command automatically handles the setup, including passing the required environment variables.

```Shell
npx @open-mcp/config add figma \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --OAUTH2_TOKEN=$OAUTH2_TOKEN \
  --X_FIGMA_TOKEN=$X_FIGMA_TOKEN
```

--------------------------------

### APIDOC: launchinstance Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `launchinstance` tool, used to provision a new instance. It requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables and a comprehensive set of parameters for instance configuration.

```APIDOC
Tool: launchinstance
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema:
  region_name: string
  instance_type_name: string
  ssh_key_names: array
  file_system_names: array
  hostname: string
  name: string
  image: other
  user_data: string
  tags: array
```

--------------------------------

### Get Configurations API

Source: https://www.open-mcp.org/servers/vercel

This API endpoint retrieves a list of configurations, allowing filtering by view, installation type, integration ID or slug, team ID, and slug. An API key is required for authentication.

```APIDOC
Environment variables:
  - API_KEY

Input schema:
  - view (string)
  - installationType (string)
  - integrationIdOrSlug (string)
  - teamId (string)
  - slug (string)
```

--------------------------------

### Install Backstage Catalog Locally for Cursor IDE

Source: https://www.open-mcp.org/servers/backstage-catalog

This command integrates the `backstage-catalog` server into the Cursor IDE's MCP client configuration. It targets the `.cursor/mcp.json` file, allowing the server to be used within Cursor projects, and includes the `API_KEY`.

```shell
npx @open-mcp/config add backstage-catalog \
  .cursor/mcp.json \
  --API_KEY=$API_KEY
```

--------------------------------

### API Endpoint: Get Library Analytics Variable Actions

Source: https://www.open-mcp.org/servers/figma

Retrieves analytics for variable actions in a library. Requires OAuth2 and Figma tokens. Input includes file key, cursor, group by, start date, and end date.

```APIDOC
Endpoint: getlibraryanalyticsvariableactions
Environment variables:
  OAUTH2_TOKEN
  X_FIGMA_TOKEN
Input schema:
  file_key (string)
  cursor (string)
  group_by (string)
  start_date (string)
  end_date (string)
```

--------------------------------

### APIDOC: postinstance Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `postinstance` tool, used to create or update an instance. It requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables, along with `id` and `name` strings as input.

```APIDOC
Tool: postinstance
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema:
  id: string
  name: string
```

--------------------------------

### Install Backstage Catalog Locally for Claude Desktop

Source: https://www.open-mcp.org/servers/backstage-catalog

This command uses the OpenMCP config CLI to add the `backstage-catalog` server to the Claude desktop client configuration. It specifies the path to the Claude desktop config file and passes the `API_KEY` environment variable.

```shell
npx @open-mcp/config add backstage-catalog \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --API_KEY=$API_KEY
```

--------------------------------

### API Endpoint: Get Library Analytics Style Actions

Source: https://www.open-mcp.org/servers/figma

Retrieves analytics for style actions in a library. Requires OAuth2 and Figma tokens. Input includes file key, cursor, group by, start date, and end date.

```APIDOC
Endpoint: getlibraryanalyticsstyleactions
Environment variables:
  OAUTH2_TOKEN
  X_FIGMA_TOKEN
Input schema:
  file_key (string)
  cursor (string)
  group_by (string)
  start_date (string)
  end_date (string)
```

--------------------------------

### Install Backstage Catalog Locally for Generic Client Config

Source: https://www.open-mcp.org/servers/backstage-catalog

This general command demonstrates how to add the `backstage-catalog` server to any OpenMCP client configuration file. Users need to replace `/path/to/client/config.json` with the actual path to their client's configuration.

```shell
npx @open-mcp/config add backstage-catalog \
  /path/to/client/config.json \
  --API_KEY=$API_KEY
```

--------------------------------

### API Endpoint: Get Library Analytics Component Actions

Source: https://www.open-mcp.org/servers/figma

Retrieves analytics for component actions in a library. Requires OAuth2 and Figma tokens. Input includes file key, cursor, group by, start date, and end date.

```APIDOC
Endpoint: getlibraryanalyticscomponentactions
Environment variables:
  OAUTH2_TOKEN
  X_FIGMA_TOKEN
Input schema:
  file_key (string)
  cursor (string)
  group_by (string)
  start_date (string)
  end_date (string)
```

--------------------------------

### APIDOC: restartinstance Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `restartinstance` tool, which restarts one or more specified instances. It requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables, and an array of `instance_ids` as input.

```APIDOC
Tool: restartinstance
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema:
  instance_ids: array
```

--------------------------------

### Install OpenMCP Swagger Petstore Locally with CLI (Generic)

Source: https://www.open-mcp.org/servers/swagger-petstore

Generic command to add the swagger-petstore server to any OpenMCP client configuration using the CLI. Specify the path to your client config file.

```Shell
npx @open-mcp/config add swagger-petstore \
  /path/to/client/config.json \
  --OAUTH2_TOKEN=$OAUTH2_TOKEN \
  --API_KEY=$API_KEY
```

--------------------------------

### Install OpenMCP Swagger Petstore Locally with CLI (Cursor)

Source: https://www.open-mcp.org/servers/swagger-petstore

Add the swagger-petstore server to your Cursor project's MCP client configuration using the OpenMCP config CLI. Run this command from your project root or home directory.

```Shell
npx @open-mcp/config add swagger-petstore \
  .cursor/mcp.json \
  --OAUTH2_TOKEN=$OAUTH2_TOKEN \
  --API_KEY=$API_KEY
```

--------------------------------

### API: Delete Installation Resources

Source: https://www.open-mcp.org/servers/vercel

Documents the 'delete_v1_installations_integrationconfigurationid_resources_res' API endpoint, detailing its required environment variables and input parameters for deleting installation resources.

```APIDOC
Endpoint: delete_v1_installations_integrationconfigurationid_resources_res
Environment Variables:
  - API_KEY
Input Schema:
  - integrationConfigurationId (string)
  - resourceId (string)
  - itemId (string)
```

--------------------------------

### API: Patch Installation Resources

Source: https://www.open-mcp.org/servers/vercel

Documents the 'patch_v1_installations_integrationconfigurationid_resources_reso' API endpoint, detailing its required environment variables and input parameters for patching installation resources.

```APIDOC
Endpoint: patch_v1_installations_integrationconfigurationid_resources_reso
Environment Variables:
  - API_KEY
Input Schema:
  - integrationConfigurationId (string)
  - resourceId (string)
  - itemId (string)
  - slug (string)
  - origin (string)
  - name (string)
  - category (string)
  - description (string)
  - isArchived (boolean)
  - createdAt (number)
  - updatedAt (number)
```

--------------------------------

### API Documentation for createprompt Endpoint

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `createprompt` API endpoint, outlining environment variables and input parameters for creating new prompts. It supports defining prompt name, content, parameters, functions, tools, model, and version details.

```APIDOC
Environment variables:
- X_PORTKEY_API_KEY

Input schema:
- name (string)
- collection_id (string)
- string (string)
- parameters (object)
- functions (array)
- tools (array)
- tool_choice (object)
- model (string)
- virtual_key (string)
- version_description (string)
- template_metadata (object)
```

--------------------------------

### agenta-ai Tool: create_account

Source: https://www.open-mcp.org/servers/agenta-ai

API documentation for the `create_account` tool. It requires `AUTHORIZATION` and takes `user` and `scope` objects as input to create a single account.

```APIDOC
create_account:
  Environment variables:
    AUTHORIZATION
  Input schema:
    user: (object)
    scope: (object)
```

--------------------------------

### API: Search for Issues Using JQL (GET)

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for searching issues using JQL via a GET request. It requires authentication and supports various parameters for query, pagination, fields, and expansion.

```APIDOC
searchforissuesusingjql:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    - jql (string)
    - startAt (integer)
    - maxResults (integer)
    - validateQuery (string)
    - fields (array)
    - expand (string)
    - properties (array)
    - fieldsByKeys (boolean)
    - failFast (boolean)
```

--------------------------------

### APIDOC: listinstances Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `listinstances` tool, used to retrieve a list of instances. This tool requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables for authentication and takes no input parameters.

```APIDOC
Tool: listinstances
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema: No input parameters
```

--------------------------------

### API: Search and Reconcile Issues Using JQL (GET)

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for searching and reconciling issues using JQL via a GET request. It requires authentication and supports pagination, fields, expansion, and issue reconciliation.

```APIDOC
searchandreconsileissuesusingjql:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    - jql (string)
    - nextPageToken (string)
    - maxResults (integer)
    - fields (array)
    - expand (string)
    - properties (array)
    - fieldsByKeys (boolean)
    - failFast (boolean)
    - reconcileIssues (array)
```

--------------------------------

### Mintlify Tool: post_plants API

Source: https://www.open-mcp.org/servers/mintlify

API documentation for the post_plants tool, including required environment variables and input parameters.

```APIDOC
post_plants:
  Environment variables:
    API_KEY
  Input schema:
    No input parameters
```

--------------------------------

### APIDOC: getinstance Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `getinstance` tool, which retrieves details for a specific instance by its ID. It requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables and an `id` string as input.

```APIDOC
Tool: getinstance
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema:
  id: string
```

--------------------------------

### Get Events API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve a list of events.

```APIDOC
Method: getevents
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  No input parameters
```

--------------------------------

### Portkey-AI Tool: servers_chat_completions

Source: https://www.open-mcp.org/servers/portkey-ai

API documentation for the `servers_chat_completions` tool, including its associated environment variables and input schema.

```APIDOC
servers_chat_completions:
  Environment variables
    * `X_PORTKEY_API_KEY`
  Input schema
    No input parameters
```

--------------------------------

### Get Policy API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve a specific policy.

```APIDOC
Method: getpolicy
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  No input parameters
```

--------------------------------

### API Endpoint: Get All Workspaces

Source: https://www.open-mcp.org/servers/portkey-ai

Retrieves a list of all admin workspaces. Supports pagination. Requires an API key.

```APIDOC
Endpoint: get_admin_workspaces
Environment Variables:
  - X_PORTKEY_API_KEY
Input Schema:
  - page_size (integer)
  - current_page (integer)
```

--------------------------------

### Mintlify Tool: get_plants API

Source: https://www.open-mcp.org/servers/mintlify

API documentation for the get_plants tool, including required environment variables and input parameters.

```APIDOC
get_plants:
  Environment variables:
    API_KEY
  Input schema:
    limit: integer
```

--------------------------------

### API: Get All Labels

Source: https://www.open-mcp.org/servers/jira

Retrieves a paginated list of all available labels in the system.

```APIDOC
getalllabels:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    startAt: integer
    maxResults: integer
```

--------------------------------

### Manually Configure OpenMCP Client for Local Backstage Catalog Server

Source: https://www.open-mcp.org/servers/backstage-catalog

This JSON snippet provides the manual configuration for an OpenMCP client to run the `backstage-catalog` server locally. It specifies the `npx` command to execute the server and includes an `env` block for environment variables like `API_KEY`.

```json
{
  "mcpServers": {
    "backstage-catalog": {
      "command": "npx",
      "args": ["-y", "@open-mcp/backstage-catalog"],
      "env": {"API_KEY":"..."}
    }
  }
}
```

--------------------------------

### Get Policies API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve multiple policies by their IDs.

```APIDOC
Method: getpolicies
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  ids (string)
```

--------------------------------

### createfinetuningjob API Endpoint

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the createfinetuningjob API endpoint, detailing required environment variables. This endpoint does not require any input parameters.

```APIDOC
Method: createfinetuningjob
Environment Variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input Schema:
  No input parameters
```

--------------------------------

### API: Get Attachment

Source: https://www.open-mcp.org/servers/jira

Retrieves an attachment by its ID. Requires authentication tokens.

```APIDOC
getattachment:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    id: string
```

--------------------------------

### API Method: listrunsteps

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `listrunsteps` API method, detailing its environment variables and input schema for retrieving a list of steps for a specific run. Parameters allow for filtering, ordering, and pagination of the results.

```APIDOC
Method: listrunsteps
Environment variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input schema:
  - thread_id (string)
  - run_id (string)
  - limit (integer)
  - order (string)
  - after (string)
  - before (string)
```

--------------------------------

### API: Get Precomputations by ID

Source: https://www.open-mcp.org/servers/jira

Retrieves specific precomputations by their IDs. Results can be ordered.

```APIDOC
getprecomputationsbyid:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    orderBy: string
    precomputationIDs: array
```

--------------------------------

### Install OpenMCP Swagger Petstore Locally with CLI (Claude Desktop)

Source: https://www.open-mcp.org/servers/swagger-petstore

Use the OpenMCP config CLI to add the swagger-petstore server to your Claude desktop client configuration. This command passes environment variables for authentication.

```Shell
npx @open-mcp/config add swagger-petstore \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --OAUTH2_TOKEN=$OAUTH2_TOKEN \
  --API_KEY=$API_KEY
```

--------------------------------

### Get Configuration API

Source: https://www.open-mcp.org/servers/jira

Retrieves the current system configuration. This endpoint requires authentication.

```APIDOC
Environment variables:
  OAUTH2_TOKEN
  USERNAME_PASSWORD_BASE64

Input schema:
  No input parameters
```

--------------------------------

### APIDOC: listinstancetypes Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `listinstancetypes` tool, which retrieves a list of available instance types. This tool requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables and takes no input parameters.

```APIDOC
Tool: listinstancetypes
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema: No input parameters
```

--------------------------------

### API: Get Priorities

Source: https://www.open-mcp.org/servers/jira

Retrieves a list of all available priorities. This endpoint does not require any input parameters.

```APIDOC
getpriorities:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema: No input parameters
```

--------------------------------

### API: Get Plan-Only Team

Source: https://www.open-mcp.org/servers/jira

Retrieves details of a specific plan-only team associated with a plan.

```APIDOC
getplanonlyteam:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    planId: integer
    planOnlyTeamId: integer
```

--------------------------------

### Create Project API

Source: https://www.open-mcp.org/servers/totoy-ai

Creates a new project with a specified name. An API key is required to perform this action.

```APIDOC
Method: createproject
Environment variables:
  API_KEY
Input schema:
  name (string)
```

--------------------------------

### API: Get Atlassian Team

Source: https://www.open-mcp.org/servers/jira

Retrieves details of a specific Atlassian team associated with a plan.

```APIDOC
getatlassianteam:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    planId: integer
    atlassianTeamId: string
```

--------------------------------

### Portkey-AI Tool: expandSchema

Source: https://www.open-mcp.org/servers/portkey-ai

API documentation for the `expandSchema` tool, which expands the input schema for another tool before it is called. It details the required input parameters.

```APIDOC
expandSchema:
  Input schema
    * `toolName` (string)
    * `jsonPointers` (array)
```

--------------------------------

### API Endpoint: servers_logs_exports_exportid_start

Source: https://www.open-mcp.org/servers/portkey-ai

API endpoint for starting log exports. Requires the X_PORTKEY_API_KEY environment variable. This endpoint has no specific input parameters.

```APIDOC
servers_logs_exports_exportid_start
  Environment variables:
    X_PORTKEY_API_KEY
  Input schema:
    No input parameters
```

--------------------------------

### Get Dashboard API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve details of a specific dashboard using its ID.

```APIDOC
Method: getdashboard
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  id (string)
```

--------------------------------

### Get Component API

Source: https://www.open-mcp.org/servers/jira

Retrieves details of a specific component by its ID. This endpoint requires authentication.

```APIDOC
Environment variables:
  OAUTH2_TOKEN
  USERNAME_PASSWORD_BASE64

Input schema:
  id (string)
```

--------------------------------

### API Documentation for createversion

Source: https://www.open-mcp.org/servers/jira

Details the API endpoint for createversion, including required environment variables and input parameters.

```APIDOC
createversion:
  Environment variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input schema:
    approvers: array
    archived: boolean
    description: string
    driver: string
    expand: string
    id: string
    issuesStatusForFixVersion: string
    moveUnfixedIssuesTo: string
    name: string
    operations: array
    overdue: boolean
    project: string
    projectId: integer
    releaseDate: string
    released: boolean
    self: string
    startDate: string
    userReleaseDate: string
    userStartDate: string
```

--------------------------------

### API: Get Teams

Source: https://www.open-mcp.org/servers/jira

Retrieves a list of teams associated with a specific plan, supporting cursor-based pagination.

```APIDOC
getteams:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    planId: integer
    cursor: string
    maxResults: integer
```

--------------------------------

### Create Assistant API

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the API endpoint for creating a new assistant, including required environment variables and various configuration parameters.

```APIDOC
Endpoint: createassistant
Environment Variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input Schema:
  - model (other)
  - name (string)
  - description (string)
  - instructions (string)
  - tools (array)
  - tool_resources (object)
  - metadata (object)
  - temperature (number)
  - top_p (number)
  - response_format (other)
```

--------------------------------

### Get All Available Dashboard Gadgets API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve a list of all gadgets that can be added to dashboards.

```APIDOC
Method: getallavailabledashboardgadgets
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  No input parameters
```

--------------------------------

### totoy-ai Server API Tools Reference

Source: https://www.open-mcp.org/servers/totoy-ai

Detailed documentation for the API tools exposed by the totoy-ai server, including their purpose, required environment variables, and input schemas.

```APIDOC
Tool: expandSchema
Description: Expand the input schema for a tool before calling the tool
Input schema:
  toolName (string)
  jsonPointers (array)
```

```APIDOC
Tool: createexplanation
Environment variables:
  API_KEY
Input schema:
  output_language (string)
  language_level (string)
  source_id (string)
  messages (array)
  markdown_response (boolean)
```

```APIDOC
Tool: createknowledgebase
Environment variables:
  API_KEY
Input schema:
  name (string)
  instructions (string)
  project_id (string)
```

```APIDOC
Tool: listknowledgebases
Environment variables:
  API_KEY
Input schema:
  No input parameters
```

```APIDOC
Tool: getknowledgebase
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
```

```APIDOC
Tool: modifyknowledgebase
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
  name (string)
  instructions (string)
  project_id (string)
```

```APIDOC
Tool: deleteknowledgebase
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
```

```APIDOC
Tool: chatwithknowledgebase
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
  output_language (string)
  language_level (string)
  messages (array)
  markdown_response (boolean)
```

```APIDOC
Tool: addknowledgebasesources
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
```

```APIDOC
Tool: listknowledgebasesources
Environment variables:
  API_KEY
Input schema:
  knowledge_base_id (string)
```

--------------------------------

### OpenMCP Swagger Petstore API Documentation

Source: https://www.open-mcp.org/servers/swagger-petstore

Detailed documentation for the OpenMCP Swagger Petstore API, including environment variables and available tools with their input schemas.

```APIDOC
Environment Variables:
  OPEN_MCP_BASE_URL: overwrites the base URL of every tool's underlying API request
  OAUTH2_TOKEN: gets sent to the API provider
  API_KEY: gets sent to the API provider

Tools:
  expandSchema:
    Description: Expand the input schema for a tool before calling the tool
    Input Schema:
      toolName: string
      jsonPointers: array

  updatepet:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      id: integer
      name: string
      category: object
      photoUrls: array
      tags: array
      status: string

  addpet:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      id: integer
      name: string
      category: object
      photoUrls: array
      tags: array
      status: string

  findpetsbystatus:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      status: string

  findpetsbytags:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      tags: array

  getpetbyid:
    Environment Variables:
      - API_KEY
      - OAUTH2_TOKEN
    Input Schema:
      petId: integer

  updatepetwithform:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      petId: integer
      name: string
      status: string

  deletepet:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      petId: integer
      api_key: string

  uploadfile:
    Environment Variables:
      - OAUTH2_TOKEN
    Input Schema:
      petId: integer
      additionalMetadata: string
```

--------------------------------

### Get All Dashboards API

Source: https://www.open-mcp.org/servers/jira

Retrieves a list of all dashboards, with options for filtering and pagination. This endpoint requires authentication.

```APIDOC
Environment variables:
  OAUTH2_TOKEN
  USERNAME_PASSWORD_BASE64

Input schema:
  filter (string)
  startAt (integer)
  maxResults (integer)
```

--------------------------------

### API: Get All System Avatars

Source: https://www.open-mcp.org/servers/jira

Retrieves all system avatars, filterable by type. Requires authentication tokens.

```APIDOC
getallsystemavatars:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    type: string
```

--------------------------------

### API Endpoint: Fetch Plans

Source: https://www.open-mcp.org/servers/agenta-ai

Documents the API endpoint for fetching available plans, including required environment variables and noting that it has no input parameters.

```APIDOC
Method: fetch_plans
Environment Variables:
  - AUTHORIZATION
Input Schema:
  No input parameters
```

--------------------------------

### API: Get Statuses

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for retrieving all available statuses. It requires authentication and has no input parameters.

```APIDOC
getstatuses:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    No input parameters
```

--------------------------------

### API Endpoint: createpromptpartial

Source: https://www.open-mcp.org/servers/portkey-ai

Creates a new prompt partial with a specified name, content, and version description.

```APIDOC
Endpoint: createpromptpartial
Environment Variables:
  - X_PORTKEY_API_KEY
Input Schema:
  - workspace_id (string)
  - name (string)
  - string (string)
  - version_description (string)
```

--------------------------------

### API: Get Precomputations

Source: https://www.open-mcp.org/servers/jira

Retrieves a paginated list of precomputations, allowing filtering by function key and ordering the results.

```APIDOC
getprecomputations:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    functionKey: array
    startAt: integer
    maxResults: integer
    orderBy: string
```

--------------------------------

### API Documentation for servers_completions Endpoint

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `servers_completions` API endpoint, specifying the environment variables required. This endpoint has no specific input parameters.

```APIDOC
Environment variables:
- X_PORTKEY_API_KEY

Input schema:
No input parameters
```

--------------------------------

### API Method: createrun

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `createrun` API method, outlining its environment variables and extensive input schema for initiating a new run within an existing thread. This method provides granular control over run configuration.

```APIDOC
Method: createrun
Environment variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input schema:
  - thread_id (string)
  - assistant_id (string)
  - model (other)
  - instructions (string)
  - additional_instructions (string)
  - additional_messages (array)
  - tools (array)
  - metadata (object)
  - temperature (number)
  - top_p (number)
  - stream (boolean)
  - max_prompt_tokens (integer)
  - max_completion_tokens (integer)
  - truncation_strategy (object)
  - tool_choice (other)
  - parallel_tool_calls (boolean)
  - response_format (other)
```

--------------------------------

### Get Default Share Scope API

Source: https://www.open-mcp.org/servers/jira

Retrieves the default share scope for filters. This operation requires authentication.

```APIDOC
Method: getdefaultsharescope
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  No input parameters
```

--------------------------------

### agenta-ai Tool: create_accounts

Source: https://www.open-mcp.org/servers/agenta-ai

API documentation for the `create_accounts` tool. This tool requires `AUTHORIZATION` as an environment variable and accepts various object types for creating users, organizations, workspaces, and projects, along with their memberships.

```APIDOC
create_accounts:
  Environment variables:
    AUTHORIZATION
  Input schema:
    users: (object)
    organizations: (object)
    workspaces: (object)
    projects: (object)
    organization_memberships: (object)
    workspace_memberships: (object)
    project_memberships: (object)
```

--------------------------------

### Get Dashboard Item Property API

Source: https://www.open-mcp.org/servers/jira

API endpoint to retrieve the value of a specific property for an item on a dashboard.

```APIDOC
Method: getdashboarditemproperty
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  dashboardId (string)
  itemId (string)
  propertyKey (string)
```

--------------------------------

### API: Get Attachment Content

Source: https://www.open-mcp.org/servers/jira

Retrieves the content of an attachment by its ID. Allows for redirection. Requires authentication tokens.

```APIDOC
getattachmentcontent:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    id: string
    redirect: boolean
```

--------------------------------

### API Method: listvectorstores

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `listvectorstores` API method, outlining its environment variables and input schema for retrieving a list of vector stores. Parameters allow for filtering, ordering, and pagination of the results.

```APIDOC
Method: listvectorstores
Environment variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input schema:
  - limit (integer)
  - order (string)
  - after (string)
  - before (string)
```

--------------------------------

### API: Get Application Role

Source: https://www.open-mcp.org/servers/jira

Retrieves a specific application role by its key. This endpoint requires basic authentication.

```APIDOC
getapplicationrole:
  Environment Variables:
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    key: string
```

--------------------------------

### API: Create Project

Source: https://www.open-mcp.org/servers/vercel

Documents the 'createproject' API endpoint, detailing its required environment variables and input parameters for creating a new project.

```APIDOC
Endpoint: createproject
Environment Variables:
  - API_KEY
Input Schema:
  - teamId (string)
  - slug (string)
  - enablePreviewFeedback (boolean)
  - enableProductionFeedback (boolean)
  - buildCommand (string)
  - commandForIgnoringBuildStep (string)
  - devCommand (string)
  - environmentVariables (array)
  - framework (other)
  - gitRepository (object)
  - installCommand (string)
  - name (string)
  - outputDirectory (string)
  - publicSource (boolean)
  - rootDirectory (string)
  - serverlessFunctionRegion (string)
  - serverlessFunctionZeroConfigFailover (other)
  - oidcTokenConfig (object)
  - enableAffectedProjectsDeployments (boolean)
```

--------------------------------

### API: Get All Workflow Schemes

Source: https://www.open-mcp.org/servers/jira

Retrieves all workflow schemes. Supports pagination. Requires OAuth2 token or username/password for authentication.

```APIDOC
Method: getallworkflowschemes

Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64

Input Schema:
  - startAt (integer)
  - maxResults (integer)
```

--------------------------------

### List Assistants API

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the API endpoint for listing assistants, including required environment variables and parameters for pagination and ordering.

```APIDOC
Endpoint: listassistants
Environment Variables:
  - API_KEY
  - X_PORTKEY_API_KEY
  - X_PORTKEY_CONFIG
  - X_PORTKEY_CUSTOM_HOST
  - X_PORTKEY_PROVIDER
  - X_PORTKEY_VIRTUAL_KEY
Input Schema:
  - limit (integer)
  - order (string)
  - after (string)
  - before (string)
```

--------------------------------

### API: Get Server Info

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for retrieving server information. It requires authentication and has no input parameters.

```APIDOC
getserverinfo:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    No input parameters
```

--------------------------------

### API: Get Plan

Source: https://www.open-mcp.org/servers/jira

Retrieves details for a specific plan using its identifier, with an option to specify group ID usage.

```APIDOC
getplan:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    planId: integer
    useGroupId: boolean
```

--------------------------------

### Install Sanity Server Locally for Claude Desktop

Source: https://www.open-mcp.org/servers/sanity

Use the OpenMCP config CLI to add the Sanity server to your Claude desktop client configuration, passing the `API_KEY` environment variable.

```shell
npx @open-mcp/config add sanity \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --API_KEY=$API_KEY
```

--------------------------------

### API Endpoint: listprompts

Source: https://www.open-mcp.org/servers/portkey-ai

Retrieves a paginated list of prompts, with optional search and filtering by collection or workspace.

```APIDOC
Endpoint: listprompts
Environment Variables:
  - X_PORTKEY_API_KEY
Input Schema:
  - collection_id (string)
  - workspace_id (string)
  - current_page (integer)
  - page_size (integer)
  - search (string)
```

--------------------------------

### API: Get My Permissions

Source: https://www.open-mcp.org/servers/jira

Retrieves the permissions of the authenticated user, optionally filtered by project, issue, or specific permission types.

```APIDOC
getmypermissions:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    projectKey: string
    projectId: string
    issueKey: string
    issueId: string
    permissions: string
    projectUuid: string
    projectConfigurationUuid: string
    commentId: string
```

--------------------------------

### Manual Configuration for Local agenta-ai Server

Source: https://www.open-mcp.org/servers/agenta-ai

Manually add the agenta-ai server configuration to your MCP client's JSON file. This setup specifies the command to run the server locally using `npx` and includes environment variables.

```json
{
  "mcpServers": {
    "agenta-ai": {
      "command": "npx",
      "args": ["-y", "@open-mcp/agenta-ai"],
      "env": {"AUTHORIZATION":"..."}
    }
  }
}
```

--------------------------------

### API: Get Approximate Application License Count

Source: https://www.open-mcp.org/servers/jira

Retrieves an approximate count of licenses for a specific application, identified by its key.

```APIDOC
getapproximateapplicationlicensecount:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    applicationKey: string
```

--------------------------------

### API: Get Approximate License Count

Source: https://www.open-mcp.org/servers/jira

Retrieves an approximate count of licenses in use. This endpoint requires no input parameters.

```APIDOC
getapproximatelicensecount:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    No input parameters
```

--------------------------------

### API: Create Screen Scheme

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for creating a new screen scheme. It requires authentication and takes description, name, and screens as input.

```APIDOC
createscreenscheme:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    - description (string)
    - name (string)
    - screens (string)
```

--------------------------------

### agenta-ai Tool: expandSchema

Source: https://www.open-mcp.org/servers/agenta-ai

API documentation for the `expandSchema` tool, which expands the input schema for another tool before its invocation. It requires `toolName` (string) and `jsonPointers` (array) as input.

```APIDOC
expandSchema:
  description: Expand the input schema for a tool before calling the tool
  Input schema:
    toolName: (string)
    jsonPointers: (array)
```

--------------------------------

### API: Get Issue Property

Source: https://www.open-mcp.org/servers/jira

Retrieves the value of a specific property from a Jira issue using its key. Authentication is required.

```APIDOC
Method: getissueproperty
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  - issueIdOrKey (string)
  - propertyKey (string)
```

--------------------------------

### API: Get Issue Property Keys

Source: https://www.open-mcp.org/servers/jira

Retrieves all property keys associated with a specific Jira issue. Authentication is required.

```APIDOC
Method: getissuepropertykeys
Environment Variables:
  - OAUTH2_TOKEN
  - USERNAME_PASSWORD_BASE64
Input Schema:
  - issueIdOrKey (string)
```

--------------------------------

### API Endpoint: listhardware

Source: https://www.open-mcp.org/servers/together-ai

Documents the 'listhardware' API endpoint, detailing its required environment variables and input schema for listing available hardware configurations.

```APIDOC
API Endpoint: listhardware
Environment variables:
  API_KEY
Input schema:
  model (string)
```

--------------------------------

### Get Component Related Issues API

Source: https://www.open-mcp.org/servers/jira

Retrieves issues related to a specific component by its ID. Authentication is required for this endpoint.

```APIDOC
Environment variables:
  OAUTH2_TOKEN
  USERNAME_PASSWORD_BASE64

Input schema:
  id (string)
```

--------------------------------

### API Endpoint: create_app

Source: https://www.open-mcp.org/servers/agenta-ai

Creates a new application. Requires authorization and details like app name, template key, project, workspace, and organization IDs.

```APIDOC
create_app:
  Environment variables:
    - AUTHORIZATION
  Input schema:
    - app_name (string)
    - template_key (other)
    - project_id (other)
    - workspace_id (other)
    - organization_id (other)
```

--------------------------------

### Install Lambda-AI Server Locally for Claude Desktop

Source: https://www.open-mcp.org/servers/lambda-ai

Command to add the lambda-ai server to the Claude desktop client configuration using the OpenMCP config CLI. This command requires the API_KEY and USERNAME_PASSWORD_BASE64 environment variables to be set.

```Shell
npx @open-mcp/config add lambda-ai \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --API_KEY=$API_KEY \
  --USERNAME_PASSWORD_BASE64=$USERNAME_PASSWORD_BASE64
```

--------------------------------

### Get Comment Property Keys API

Source: https://www.open-mcp.org/servers/jira

Retrieves all property keys associated with a specific comment. This operation requires authentication.

```APIDOC
Environment variables:
  OAUTH2_TOKEN
  USERNAME_PASSWORD_BASE64

Input schema:
  commentId (string)
```

--------------------------------

### API: Get Available Transitions

Source: https://www.open-mcp.org/servers/jira

Retrieves available transitions for specified issues. Allows pagination. Requires authentication tokens.

```APIDOC
getavailabletransitions:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    issueIdsOrKeys: string
    endingBefore: string
    startingAfter: string
```

--------------------------------

### APIDOC: terminateinstance Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `terminateinstance` tool, used to terminate one or more specified instances. It requires `API_KEY` and `USERNAME_PASSWORD_BASE64` environment variables, and an array of `instance_ids` as input.

```APIDOC
Tool: terminateinstance
Environment variables:
  API_KEY
  USERNAME_PASSWORD_BASE64
Input schema:
  instance_ids: array
```

--------------------------------

### API: Get Attachment Metadata

Source: https://www.open-mcp.org/servers/jira

Retrieves metadata for an attachment. This endpoint requires authentication tokens but no specific input parameters.

```APIDOC
getattachmentmeta:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    No input parameters
```

--------------------------------

### Install Lambda-AI Server Locally for Other Clients

Source: https://www.open-mcp.org/servers/lambda-ai

Generic command to add the lambda-ai server to any OpenMCP client configuration using the OpenMCP config CLI. Replace `/path/to/client/config.json` with the actual path to your client's configuration file.

```Shell
npx @open-mcp/config add lambda-ai \
  /path/to/client/config.json \
  --API_KEY=$API_KEY \
  --USERNAME_PASSWORD_BASE64=$USERNAME_PASSWORD_BASE64
```

--------------------------------

### Set API Key Environment Variable Locally

Source: https://www.open-mcp.org/servers/together-ai

Instructions for setting the API_KEY environment variable in the shell before local server installation.

```shell
API_KEY='...'
```

--------------------------------

### APIDOC: expandSchema Tool

Source: https://www.open-mcp.org/servers/lambda-ai

Documentation for the `expandSchema` tool, which expands the input schema for another tool before it is called. It requires the `toolName` and an array of `jsonPointers` as input.

```APIDOC
Tool: expandSchema
Description: Expand the input schema for a tool before calling the tool
Input schema:
  toolName: string
  jsonPointers: array
```

--------------------------------

### Get Certificates API

Source: https://www.open-mcp.org/servers/vercel

Retrieves a list of certificates. No environment variables or input parameters are required for this endpoint.

```APIDOC
Method: get_certs
Environment Variables:
  No environment variables required
Input Schema:
  No input parameters
```

--------------------------------

### Add Local Mintlify Server to OpenMCP Client via CLI

Source: https://www.open-mcp.org/servers/mintlify

Use the OpenMCP config CLI to add the locally running Mintlify server to your client configuration. This snippet shows examples for Claude desktop, Cursor, and a generic path, passing the API_KEY.

```bash
npx @open-mcp/config add mintlify \
  ~/Library/Application\ Support/Claude/claude_desktop_config.json \
  --API_KEY=$API_KEY
```

```bash
npx @open-mcp/config add mintlify \
  .cursor/mcp.json \
  --API_KEY=$API_KEY
```

```bash
npx @open-mcp/config add mintlify \
  /path/to/client/config.json \
  --API_KEY=$API_KEY
```

--------------------------------

### Get Project Domain API

Source: https://www.open-mcp.org/servers/vercel

API endpoint to retrieve details of a specific domain associated with a project.

```APIDOC
Endpoint: getprojectdomain
Environment Variables:
  - API_KEY
Input Schema:
  idOrName: string
  domain: string
  teamId: string
  slug: string
```

--------------------------------

### API Documentation for createcompletion Endpoint

Source: https://www.open-mcp.org/servers/portkey-ai

Documents the `createcompletion` API endpoint, outlining the necessary environment variables and the input schema for generating text completions. This endpoint provides parameters for controlling the completion output.

```APIDOC
Environment variables:
- API_KEY
- X_PORTKEY_API_KEY
- X_PORTKEY_CONFIG
- X_PORTKEY_CUSTOM_HOST
- X_PORTKEY_PROVIDER
- X_PORTKEY_VIRTUAL_KEY

Input schema:
- model (other)
- prompt (other)
- best_of (integer)
- echo (boolean)
- frequency_penalty (number)
- logit_bias (object)
- logprobs (integer)
- max_tokens (integer)
- n (integer)
- presence_penalty (number)
- seed (integer)
- stop (other)
- stream (boolean)
- stream_options (object)
- suffix (string)
- temperature (number)
- top_p (number)
- user (string)
```

--------------------------------

### API: createproject

Source: https://www.open-mcp.org/servers/jira

Documents the API endpoint for creating a new project, including required environment variables and input parameters for defining project details.

```APIDOC
createproject:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    - assigneeType (string)
    - avatarId (integer)
    - categoryId (integer)
    - description (string)
    - fieldConfigurationScheme (integer)
    - issueSecurityScheme (integer)
    - issueTypeScheme (integer)
    - issueTypeScreenScheme (integer)
    - key (string)
    - lead (string)
    - leadAccountId (string)
    - name (string)
    - notificationScheme (integer)
    - permissionScheme (integer)
    - projectTemplateKey (string)
    - projectTypeKey (string)
    - url (string)
    - workflowScheme (integer)
```

--------------------------------

### Get Organization API

Source: https://www.open-mcp.org/servers/totoy-ai

Retrieves details of the organization. This operation does not require any input parameters, only an API key for authentication.

```APIDOC
Method: getorganization
Environment variables:
  API_KEY
Input schema:
  No input parameters
```

--------------------------------

### Get Add-on Properties Resource

Source: https://www.open-mcp.org/servers/jira

Retrieves all properties for a specific add-on. This operation requires authentication tokens and the 'addonKey' to identify the add-on.

```APIDOC
addonpropertiesresource_getaddonproperties_get:
  Environment Variables:
    - OAUTH2_TOKEN
    - USERNAME_PASSWORD_BASE64
  Input Schema:
    - addonKey (string)
```

--------------------------------

### Create Source API

Source: https://www.open-mcp.org/servers/totoy-ai

Creates a new source with specified content, title, backlink, validity period, project ID, and custom metadata. An API key is required for this operation.

```APIDOC
Method: createsource
Environment variables:
  API_KEY
Input schema:
  text_content (string)
  title (string)
  backlink (string)
  valid_from (string)
  valid_until (string)
  project_id (string)
  custom_metadata (object)
```