Integration

Altium 365 integration

Altium 365 is Altium's cloud platform for PCB design collaboration, reached through the Nexar API. An agent can list workspaces, members and projects, read a project's parameters, commit history, releases, bills of materials and comment threads, search the component library and read part choices, manage project and workspace tasks and their comments, set project and component parameters, export Gerber, IDF or NC Drill files, and launch or terminate design workflows. Left out: supply (Octopart) part data, which counts against a part limit and needs another scope; creating, editing or deleting comment threads and comments; file uploads (projects, footprints, symbols, datasheets, component releases), which go through a separate files service; user, group, folder and permission administration; life cycle and naming scheme setup; manufacture packages. Every call acts as the signed-in user, with that user's Altium 365 permissions. The API is GraphQL. Authentication is OAuth 2.0 sign-in with your Altium 365 account through your own Nexar app with the Design scope; access tokens last 24 hours and the connection asks for offline access to renew them.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Altium 365.Built from the 33 Altium 365 tools below, on the connection you add once.

What you can do with Altium 365

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Task, 6 operations

  • create_project_taskCreate project taskPOSTAgents: ask firstCreates a task in an Altium 365 project. Returns the new task (its id is the taskId other tools take). Check errors: a non-empty list means Altium 365 refused it.
  • create_workspace_taskCreate workspace taskPOSTAgents: ask firstCreates a workspace-level task (not tied to a project) in an Altium 365 workspace. Returns the new task. Check errors: a non-empty list means Altium 365 refused it.
  • delete_taskDelete taskPOSTAgents: ask firstDeletes an Altium 365 task. Check errors: a non-empty list means Altium 365 refused it.
  • list_project_tasksList project tasksPOSTAgents: ask firstLists the tasks of an Altium 365 project, page by page: node id (the taskId other tools take), task number, name, description, priority, status, assignee, dates and comments. Includes people's names.
  • list_workspace_tasksList workspace tasksPOSTAgents: ask firstLists the workspace-level tasks of an Altium 365 workspace (tasks not tied to a project), page by page: node id, number, name, description, priority, status, assignee, dates and comments. Includes people's names.
  • update_taskUpdate taskPOSTAgents: ask firstChanges an Altium 365 task: name, description, priority, status or assignee. Only the fields you send change. Check errors: a non-empty list means Altium 365 refused it.

Component, 4 operations

  • get_componentGet componentPOSTAgents: ask firstReturns one Altium 365 library component: revision and item parameters, symbols, footprints, datasheets, and part choices with supplier prices and stock.
  • list_library_componentsList library componentsPOSTAgents: ask firstLists the components of an Altium 365 workspace library, page by page: id (the componentId other tools take), name, description, comment, type, folder and manufacturer part numbers.
  • update_component_item_parametersUpdate component item parametersPOSTAgents: ask firstAdds or changes item parameters of an Altium 365 library component, without creating a new revision. With replaceExisting true, every item parameter not sent is removed. Check errors: a non-empty list means Altium 365 refused it.
  • update_component_revision_parametersUpdate component revision parametersPOSTAgents: ask firstChanges revision parameters of an Altium 365 library component: this creates a NEW component revision, and the component gets a new id (returned as componentId). Check errors: a non-empty list means Altium 365 refused it.

Project, 3 operations

  • get_projectGet projectPOSTAgents: ask firstReturns one Altium 365 project: name, description, type, web address, dates, creator and last editor (names), parameters, and its design variant names (the variantName get_wip_variant_bom takes).
  • list_projectsList projectsPOSTAgents: ask firstLists the projects of an Altium 365 workspace, page by page: node id (the projectId other tools take), reference id, name, description, type, web address, dates and variant count.
  • update_project_parametersUpdate project parametersPOSTAgents: ask firstAdds or changes parameters of an Altium 365 project (a name/value list). With replaceExisting true, every user parameter not sent is removed. Does not create a revision. Check errors: a non-empty list means Altium 365 refused it.

Task comment, 3 operations

  • create_task_commentCreate task commentPOSTAgents: ask firstAdds a comment to an Altium 365 task. Returns the new comment (its commentId). Check errors: a non-empty list means Altium 365 refused it.
  • delete_task_commentDelete task commentPOSTAgents: ask firstDeletes a comment from an Altium 365 task. Check errors: a non-empty list means Altium 365 refused it.
  • update_task_commentUpdate task commentPOSTAgents: ask firstReplaces the text of a comment on an Altium 365 task. Check errors: a non-empty list means Altium 365 refused it.

Workflow, 3 operations

  • launch_workflowLaunch workflowPOSTAgents: ask firstStarts a real Altium 365 workflow from a definition (an automated design process such as a review or approval); depending on its definition it can assign tasks to workspace members. Returns the workflow id.
  • list_workflowsList workflowsPOSTAgents: ask firstLists the workflows (running or ended design processes) of an Altium 365 workspace: id, name, definition, status, active step, assignee, creator and dates.
  • terminate_workflowsTerminate workflowsPOSTAgents: ask firstTerminates running Altium 365 workflows. Check errors: each entry names a workflow id that was not terminated and why.

Bom, 2 operations

  • get_release_variant_bomGet release variant bomPOSTAgents: ask firstReturns the bill of materials of one variant of a released Altium 365 design, page by page, with the download link of the release package.
  • get_wip_variant_bomGet wip variant bomPOSTAgents: ask firstReturns the bill of materials of one design variant of an Altium 365 project (work in progress), page by page: quantity, component, manufacturer part numbers and designators.

Comment thread, 2 operations

  • get_comment_threadGet comment threadPOSTAgents: ask firstReturns one comment thread of an Altium 365 project with all its replies, status (0 resolved, 1 active), author, assignee and document context. Includes people's names.
  • list_comment_threadsList comment threadsPOSTAgents: ask firstLists the comment threads of an Altium 365 project with their replies: number, status (0 resolved, 1 active), author, assignee, document context, dates and comment texts. Includes people's names.

Commit, 2 operations

  • get_project_latest_commitGet project latest commitPOSTAgents: ask firstReturns the latest version-control commit of an Altium 365 project: revision id, message, author, date and the files it added, modified or deleted.
  • list_project_commitsList project commitsPOSTAgents: ask firstLists the version-control commits of an Altium 365 project, page by page: revision id, message, author, date and changed files.

Project export job, 2 operations

  • create_project_export_jobCreate project export jobPOSTAgents: ask firstStarts a job that exports Altium 365 project data (Gerber, Gerber X2, IDF, NC Drill, or any OutJob). Returns projectExportJobId: poll get_project_export_job until DONE for the zip link. Check errors: a non-empty list means Altium 365 refused it.
  • get_project_export_jobGet project export jobPOSTAgents: ask firstReturns the status of an Altium 365 project export job (PENDING, PROCESSING, DONE or ERROR), the zip download link once DONE, or the error message once ERROR. Call again until it ends.

Release, 2 operations

  • get_releaseGet releasePOSTAgents: ask firstReturns one release of an Altium 365 project: release id, description, date, and each variant with the download link of its release package.
  • list_project_releasesList project releasesPOSTAgents: ask firstLists the releases (published versions with manufacturing files) of an Altium 365 project, page by page: release id, description, date and variant names.

Team, 1 operation

  • get_workspace_teamGet workspace teamPOSTAgents: ask firstReturns the members of an Altium 365 workspace (user id, user name, email, first and last name, groups) and its user groups. Personal data of the workspace members.

User, 1 operation

  • get_current_userGet current userPOSTAgents: ask firstReturns the signed-in Altium 365 user: workspace user id, global user id, user name, email, first and last name, and user groups. Personal data.

Workflow definition, 1 operation

  • list_workflow_definitionsList workflow definitionsPOSTAgents: ask firstLists the workflow definitions (automated design processes such as review or approval) of an Altium 365 workspace, with the variables each needs to be launched by launch_workflow.

Workspace, 1 operation

  • list_workspacesList workspacesPOSTAgents: ask firstLists the Altium 365 workspaces the signed-in user belongs to: name, web address (url, the workspaceUrl other tools take), description, default flag and hosting region.

Use Altium 365 from Claude Code, Cursor or Codex

Connect Altium 365 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Altium 365 operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Altium 365

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Altium 365 once

    Add your Altium 365 connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Altium 365 integration FAQ

What can you do with the Altium 365 integration?

LiveContext exposes 33 operations on Altium 365, covering task, component, project and task comment.

Popular integrations

Browse the whole catalog