Configure tools and MCP servers
MCP server examples
Use these examples to configure MCP servers in MCP Tools
GitHub
In this example, INXM Local runs mcp-remote locally to connect to GitHub's hosted MCP server using your personal access token (PAT).
Why a PAT and not OAuth?
INXM Local's remote HTTP OAuth flow with a blank client ID uses dynamic client registration, which GitHub's MCP server does not support. The local proxy passes the PAT as a bearer token instead. This limitation is specific to GitHub's endpoint; other servers may support dynamic registration.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Local stdio |
| Name | GitHub |
| Server command | npx |
| Server args | -y mcp-remote https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer ${GITHUB_TOKEN}" |
| Server env | GITHUB_TOKEN=ghp_yourTokenHere |
- Make sure Node.js is installed and
npxis available. - Create a GitHub PAT with the permissions needed for the tools you plan to use. Replace
ghp_yourTokenHerein Server env with your token. This value is saved in the local tool catalog; protect that file and do not commit it to a repository. - In MCP Tools, click + Add and enter the fields above. Click List tools on server, then select and import the tools you need. When in doubt, refer to the guide on local stdio.
Granola
Granola supports browser-based OAuth without a pre-registered client ID.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Remote HTTP |
| Name | Granola |
| Remote endpoint | https://mcp.granola.ai/mcp |
| Connect with OAuth | Checked |
| Public client ID | Leave blank |
- In MCP Tools, click + Add and enter the fields above.
- Click Connect, then click on Open authorization page when the link appears. Sign in to Granola and authorize access in your browser.
- Once the connection shows Connected, INXM Local lists the tools automatically. Select the ones you need and click Import N selected. For more details, refer to the guide on Remote HTTP.
Notion
Notion's hosted MCP server connects to your workspace through browser-based OAuth.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Remote HTTP |
| Name | Notion |
| Remote endpoint | https://mcp.notion.com/mcp |
| Connect with OAuth | Checked |
| Public client ID | Leave blank |
- In MCP Tools, click + Add and enter the fields above.
- Click Connect, then Open authorization page when the link appears. Sign in to Notion and authorize access to the workspace you want to use.
- Once the connection shows Connected, INXM Local lists the tools automatically. Select the ones you need and click Import N selected. See Remote HTTP for more details.
Linear
Linear's hosted MCP server connects to your workspace through browser-based OAuth.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Remote HTTP |
| Name | Linear |
| Remote endpoint | https://mcp.linear.app/mcp |
| Connect with OAuth | Checked |
| Public client ID | Leave blank |
- In MCP Tools, click + Add and enter the fields above.
- Click Connect, then Open authorization page when the link appears. Sign in to Linear and authorize access to your workspace.
- Once the connection shows Connected, INXM Local lists the tools automatically. Select the ones you need and click Import N selected. See Remote HTTP for more details.
Slack
This example runs the Slack MCP server locally with a user OAuth token from a Slack app installed in your workspace.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Local stdio |
| Name | Slack |
| Server command | npx |
| Server args | -y slack-mcp-server@latest --transport stdio |
| Server env | SLACK_MCP_XOXP_TOKEN=xoxp-your-token-here |
- Make sure Node.js is installed and
npxis available. - Login at Slack API apps, create a Blank app and choose the workspace where you want to install it.
- In the app's left sidebar, open OAuth & Permissions. Under User Token Scopes, select the scopes needed for the Slack features you plan to use. For example, an app might use:
channels:history,channels:read,channels:writegroups:history,groups:readim:history,im:read,im:writempim:history,mpim:read,mpim:writeusers:readchat:writesearch:readusergroups:read,usergroups:write
- Scroll up to Install to Workspace (or Install App) and approve the permissions. Copy the User OAuth Token (starting with
xoxp-) from the same OAuth & Permissions page. - In INXM Local MCP Tools, click + Add and enter the fields above, replacing
xoxp-your-token-herein Server env with your token. Click List tools on server, then select and import the tools you need. See Local stdio for more details. The token is saved in the local tool catalog; protect that file and do not commit it to a repository.
Microsoft 365
In this case, a single server configuration covers multiple M365 services, so you can choose their tools from one server.
Tool selection and optional server flags
With no extra flags, the command below offers personal-account tools by default. This includes Outlook mail and calendar, contacts, OneDrive, Excel, OneNote, To Do, Planner, profile, and search.
To change what the server offers, append flags to Server args:
--org-modeenables work/school features such as Teams, SharePoint, meetings, and shared mailboxes. Without it, those tools are not offered.--org-modeworks as a switch; do not pass an email address, tenant ID, ortrueafter it.--preset [NAME]limits the offered tools to a named category. Use comma-separated names to combine categories, for example--preset mail,calendar. Presets do not enable work/school features on their own; add--org-modewhen those tools are needed.
Available presets: mail, calendar, files, personal, work, excel, contacts, tasks, onenote, search, users, outlook, onedrive, teams, teams-write, all. See the Softeria preset documentation for the most up-to-date list, or run npx @softeria/ms-365-mcp-server --list-presets.
Presets still filter tools with --org-mode. Your account permissions may limit what you can use.
| Field | Value |
|---|---|
| Kind | MCP server |
| Transport | Local stdio |
| Name | m365 |
| Server command | npx |
| Server args | -y @softeria/ms-365-mcp-server |
- Make sure Node.js is installed and
npxis available. - In MCP Tools, click + Add and enter the fields above. Click List tools on server, then select and import the tools you need. See Local stdio for more details.