Connect your account.
Sign in through Intergraph, then authorize a tool account through its provider.
An Intergraph service · Private pilot
Connect your tools once. Choose what each AI assistant can do.
One place to manage account access across your assistants, apps, and agents. Clear permissions. A way to turn them off.
Invitation required. The first pilot is read-only.
Example connections—not a claim of client certification or live service availability.
A clear connection
Account access shouldn’t be a guessing game. Toolisman separates connecting a tool from giving an assistant permission to use it.
Sign in through Intergraph, then authorize a tool account through its provider.
Choose the accounts and read actions that this executor may use.
Your assistant requests approved actions. Toolisman checks permission and returns the result.
Review activity and revoke future access without disconnecting every other assistant.
Permission is the product
Give an executor access to the accounts and actions it needs. Keep the rest outside that connection.
Understand the boundariesPermissions belong to an executor and account connection. New actions don’t silently join an old approval.
Tool credentials stay with Toolisman or the configured provider. Executors receive Toolisman access tokens.
Invocation records show action metadata—not your searches, messages, or file contents.
Start with the familiar
Files & documents
Find files and read text files or Google Docs. Attachments and unsupported binary formats are outside the first pilot.
Read-only · live verification pending
Search messages and read their headers and text. Sending, deletion, and attachments are outside the first pilot.
Read-only · live verification pending
Initial implementation, not a public integration launch. Each provider and service must pass live pilot verification before activation.
Built for choice
The consuming app’s operator selects an implementation. Your assistant uses the same Tool Protocol interface.
Toolisman connects directly to the service, with specialized adapters where deeper support matters.
An aggregator can provide broader coverage behind the same contract. Its connections require separate consent and live verification.
Portable access isn’t a promise that data never moves. Requested content goes to your approved executor and, when configured, One. Read how data flows →
A few good questions
No. Your assistant does the reasoning and work. Toolisman checks its permissions and routes tool requests through the configured implementation. An executor is an assistant, app, or agent making those requests.
No. Toolisman can serve assistants, applications, games, and other executors independently. Daemons can separately hold the instructions, tasks, and memory for work that continues across assistants.
No. Content you request passes through Toolisman and reaches the executor you approve. When the application uses One, content also passes through One. Review the executor’s and provider’s data practices before granting access.
No. Connecting the account and approving an executor are separate steps. Each executor gets its own account-specific permissions. New actions need fresh approval.
Yes. Revoke an executor, remove a tool connection, or disconnect an upstream account. These controls stop future authorized access; they cannot retract content already delivered or undo requests already sent.
Toolisman is a private pilot. Drive and Gmail search/read are the initial implementation; live provider verification is still pending. One and additional services remain disabled until their pilot checks pass. See the services page for the reviewed status.
Your next connection
Open the console to manage your tools and executor access.
Private pilot · invitation required