Integrating with External Tools
This page explains how to integrate with external tools using Agentiqs.
You can integrate with various tools such as Microsoft Office and GitHub (/docs/reference/tools).
As representative examples, we will explain the procedures for integrating with GitHub and with an MCP server.
Integrating with Applications and Web Services
Here, we will explain the procedure for integrating with GitHub using Agentiqs.

- Click [Tools] > [Create New].
- The [Tool Gallery] dialog box will appear.
- Select [GitHub] from the list.
- The GitHub settings screen will appear.
- Enter your Personal Access Token in the [GitHub API Key] field.
- Your authentication information will be saved, and you will be able to connect to GitHub.
- Add the tool you created to the AI agent.
- You will be able to access and update GitHub data in chats using that agent.
- For a list of tools available in Agentiqs, please refer to Tool List.
Integrating with an MCP Server
This section explains the setup procedure for using an MCP server with Agentiqs. Since Agentiqs does not provide an MCP server, users need to create and manage one themselves.
- The user must have created and be running an MCP server compliant with the MCP specification.
- The user must know the information needed to connect to the MCP server (hostname/port, connection method, authentication information if necessary, etc.).
- The MCP server must be on a network reachable from Agentiqs.

- Click [Tools] > [New].
- The [Tool Gallery] dialog box will appear.
- Select [Mcp Tool] from the list.
- The MCP server settings screen will appear.
- Enter the [MCP Server Settings] referring to the example settings below.
- Click the [Save] button to save the settings.
- The creation and operation of the MCP server is the user's responsibility.
- Agentiqs does not guarantee the operation or availability of the MCP server.
Example Settings
In Agentiqs' [MCP Server Settings], enter only the settings for the single server you want to use, extracted from mcpServers, rather than the entire MCP server configuration file.
Example of the entire configuration file:
{
"mcpServers": {
"exampleServer": {
"command": "npx",
"args": [
"-y",
"example-mcp-server"
]
},
"anotherServer": {
"url": "http://localhost:9000/sse"
}
}
}
Example of input:
When using exampleServer (mcpServers.exampleServer):
{
"command": "npx",
"args": [
"-y",
"example-mcp-server"
]
}
When using anotherServer (mcpServers.anotherServer):
{
"url": "http://localhost:9000/sse"
}