Skip to main content

​
External Integrations

Neural Factory uses the Model Context Protocol (MCP) to integrate with external services. These integrations give agents the ability to interact with your organization’s existing tools — creating Jira tickets, searching Confluence, sending Outlook emails, and more.

​
Available integrations

​
Jira

  • Search for issues by project, status, or keyword
  • Create new issues with title, description, and metadata
  • Update issue status, assignee, or comments
  • Read issue details and comments

​
Confluence

  • Search pages by space, title, or content
  • Read page content
  • Useful for agents that need access to internal wikis and documentation

​
Tempo

Time tracking and team analytics on top of Jira.
  • Report logged time for a person, a team, or a project, grouped by person, issue, project, day, week, or month
  • Measure utilization against each person’s real Tempo schedule, so holidays and part-time contracts are accounted for
  • Find the working days where someone logged less time than their schedule required
  • Check timesheet approval status per approval period
  • List Tempo teams, their members, and a person’s schedule
  • Read individual worklog entries when a specific entry has to be inspected
Tempo returns numeric issue ids and account ids rather than issue keys and names, so this integration reads Jira as well and needs both sets of credentials. The Tempo API token is generated in Tempo under Settings → API Integration, and it acts as the user who issued it: a report covering a whole team needs a user who can view all worklogs. The base URL has to match your Tempo data region. All Tempo tools are read-only — agents can report on time, not log or change it. Structure by Tempo is covered by the same integration, and is optional: add a Structure personal access token (generated in Jira under the Structure app’s personal settings) and the agent can also:
  • List the structures the credentials can see, with a link to open each one in Jira
  • Read a structure’s metadata, owner, and default view
  • Inspect a view’s columns, including the Tempo logged-time and planned-time columns and the team, role, and billable filters behind them
Structure’s Cloud API exposes structures and view configurations only; it cannot return rows, hierarchy contents, or computed column values. An agent asked for the numbers in a structure reports what the view measures and gets the figures themselves from the Tempo tools. Without a Structure token, the Structure tools report that Structure is not configured and everything else keeps working.

​
Outlook

  • Send emails on behalf of the authenticated user
  • Search the user’s inbox
  • Read email content
  • Useful for agents that handle communication tasks

​
SharePoint (Toolkit)

  • Search document libraries beyond what’s in a knowledge base
  • Read document content directly
  • List files and folders

​
Google Drive (Toolkit)

  • Search across Drive for files
  • Read document content
  • List files in folders

​
Custom MCP servers

Neural Factory supports dynamically loaded external MCP servers. This means your organization can build custom integrations for any internal tool or API and connect them as toolkits. A custom MCP server is reached over streamable HTTP, SSE, or a local stdio command, and can be protected in one of three ways:
  • None — access is controlled by the network alone, for example a server on a private VPN.
  • API Key — a shared key sent in a header of your choice on every request.
  • OAuth2 Client Credentials — for a server published behind an API gateway. You provide the gateway’s token URL, a client ID, an optional scope, and the client secret. Neural Factory obtains an access token from the token URL, caches it until shortly before it expires, and sends it as a bearer token on every request. The client secret is used only to request tokens; it is never forwarded to the MCP server.
Credential Values are separate from this: they are downstream secrets the MCP server itself needs (a database connection string, an internal API’s client ID) and are forwarded to the server on every request. Send user email to server. When this is enabled on a custom MCP toolkit, every tool call carries the email and user ID of the person the agent is working for, in the MCP request metadata (_meta) under the keys neuralfactory.ai/user_email and neuralfactory.ai/user_id. The server can use them to return only that user’s data, for example as a parameter of its database queries. The values are stated by Neural Factory on the user’s behalf; the server knows Neural Factory authenticated itself, not that the user did. It is off by default: enable it only for servers you trust with this personal data. The integrations Neural Factory provides (SharePoint, Google Drive, Jira, Confluence, Tempo, Outlook) always receive it. The identity is sent the same way whether the agent is used in the web app or called through the API, and over every transport (streamable HTTP, SSE, stdio).

​
How integrations work

  1. An administrator configures the integration in the Toolkits section
  2. Authentication is set up (OAuth, API keys, or other credentials)
  3. The toolkit is enabled for specific agents
  4. When a user interacts with the agent, the agent can call the integration’s tools as needed

​
Security

  • All external tool calls are authenticated and logged
  • Credentials are stored securely and never exposed to users or in conversation logs
  • Tool usage is visible in the analytics dashboard