Think-Act connects to trusted local tools through the Model Context Protocol (MCP), turns useful workflows into reusable skills, and shows which capabilities are available. It uses only the integrations you install, enable, and approve.
Available for 64-bit Windows 10 and Windows 11. macOS is planned.
Integrations Dashboard Screenshot
Recommended: 1200 × 900
These do different jobs. A skill tells the agent how to approach a task. A connector lets it work with an external system. Security policy decides whether an action can proceed, needs approval, or must be blocked.
Layer 1
Local playbooks that shape how the agent thinks, formats output, and approaches a specific workflow. They do not execute actions on their own. Built-in skills cover research, writing, review, planning, and productivity. Imported skills should be reviewed before use.
Layer 2 · Active Today
MCP servers that run locally on your device. They may require Node.js, Python, or another runtime. They can access files, credentials, networks, or apps you expose to them. Their tools are passed to the agent only when the server is enabled and connected.
Layer 3
Every tool call passes through a security gate before it can act. Read-only lookups may proceed automatically. Write actions, network calls, and anything touching real data should require confirmation or approval. If a connector is not needed, disable it.
Example: review a folder of project notes
A review skill defines the checks and the summary format. A filesystem connector supplies the notes. Policy can allow reading while asking for approval before any file is changed. If the connector is unavailable, Think-Act explains what is missing instead of claiming it reviewed the files.
MCP Connector Dashboard
Recommended: 1440 × 900
Local MCP servers run on your computer and expose a defined set of tools to Think-Act. Depending on the server, they may need Node.js, npx, Python, credentials, or access to a local application.
Runs on your device
May require Node.js, npx, Python, or another local runtime.
Controlled per connector
Enable, disable, test, and remove connectors at any time.
Trust before installation
Third-party packages are not audited by PixLab. Review every package before adding it.
Connection state stays visible
If a connector fails, its tools are removed from the available list until it reconnects.
Tools from an MCP connector are available to the agent only while the server is enabled and connected. Disable a connector when a task no longer needs it.
Find a compatible stdio MCP package through the marketplace, or configure your own server manually. Both paths require trust confirmation before installation and keep duplicate packages blocked.
Path A
Marketplace Search Screenshot
Recommended: 1200 × 600
Search compatible stdio MCP packages by name or capability. Think-Act blocks duplicate installations and shows required configuration before you commit. Every package requires a trust confirmation step before the first run.
Path B
Custom Server Config Screenshot
Recommended: 1200 × 600
Point Think-Act at a local stdio MCP server you control. Provide the command, arguments, and any environment variables it needs. Custom servers follow the same installation checks and connection controls as marketplace packages.
Trust confirmation before every new installation
Think-Act shows a trust confirmation prompt before installing any new connector, whether from the marketplace or a manual configuration. This is your chance to verify the package source, review what the server requires, and decide whether it belongs on your machine. There is no silent installation.
Skills are local playbooks stored on your device. They tell the agent how to approach a type of work — the sequence to follow, the checks to perform, the style to use — without performing actions themselves. For real actions, a skill needs a connector.
Built-in coverage
Research, review, planning, writing, security, and productivity workflows included.
Safety modes
Manual, read-only, or connector-required modes keep skills from overstepping their bounds.
Import with care
Imported skills should be reviewed before use. Read the logic, not just the name.
Connector-aware
Skills that need real tool access will declare the connector they require, not silently fail.
Skill execution flow
Skills Manager Screenshot
Recommended: 1440 × 900
Imported skills should be reviewed before use. A skill that references a connector you haven’t installed will tell the agent to recommend adding it — not proceed without it.
Think-Act builds its available tool list from live connector state. A missing or failed connector is reported plainly instead of being treated as a successful action.
Condition 1
The local MCP server or connector must be installed on the device before any tools it exposes are available to the agent.
Condition 2
You confirm trust before installation. Third-party local MCP packages are not controlled by PixLab. Only install what you have verified.
Condition 3
Connectors can be enabled and disabled at any time. A connector that is off exposes no tools to the agent regardless of what it can do.
Condition 4
A failed connector is disabled rather than silently degraded. The agent works only with connections that are confirmed live.
An enabled connector may be able to read or change data on your machine or network. Use the available controls to limit what is enabled, turn off access when a task is finished, and follow the local MCP security guidance.
Most tasks do not require a connector. Get familiar with what Think-Act can do before exposing it to anything real.
Install on a supported 64-bit Windows machine. Sign in with your PixLab account. No connector setup required to get started.
View Think-Act DownloadsWriting, OCR, summarization, and agent tasks from pasted text all work out of the box. Get a feel for what the agent can actually do before touching integrations.
Identify a workflow that genuinely requires tool access, then search for or configure a compatible local MCP server. Confirm trust before installation. Enable it only for the tasks that need it.
Review each tool call before it writes, sends, or modifies something real. Disable the connector when you are finished. Check logs if anything behaves unexpectedly.
If integrations become part of your daily workflow, upgrade to Pro or Business before running into free-tier limits on heavier use or larger teams.
Think-Act’s current integration model centers on trusted local MCP servers, local skills, explicit permissions, and visible activity. Managed cloud connectors and organization-level controls are planned after those foundations prove stable.
These are roadmap items, not current product capabilities. Do not rely on them when planning production integrations today.
A curated registry of cloud-hosted connectors that teams can enable without maintaining a local runtime.
Organization-level connector policies, managed authentication, and shared access controls.
Subscription-aware access, billing integration, and managed provisioning for enterprise connectors.
Admin controls over which connectors are available, with approvals and connection visibility carried forward.
Delegation to trusted remote agents after the connector security layer has proven stable.
Answers about local MCP, skills, connector trust, and what is available today. More product questions are covered on the full FAQ page.
Try Think-Act with Local MCPNo. Third-party local MCP packages are not controlled, audited, or endorsed by PixLab. Think-Act shows a trust confirmation before installation, but you are responsible for reviewing the source, permissions, commands, and configuration. Read the connector security guidance before adding a package with access to sensitive files or services.
No. The current release uses local MCP servers and local skills. Cloud MCP, managed authentication, organization policies, and A2A remote agents remain roadmap items. See the enterprise connector roadmap for the planned scope.
No. Skills describe the method; connectors provide real tools. A skill that needs an external action should declare the required connector. If that connector is unavailable, Think-Act reports what is missing rather than pretending the action happened. See task automation for practical workflow examples.
A failed connector is disabled and removed from the available tool list. Think-Act does not silently use a broken connection. Review the activity log, correct the configuration, and re-enable the connector after its connection check passes. The Security & Recovery page covers related review controls.
No. Many useful workflows work without a connector, including Writing Assist, OCR & Documents, and the Screen Recorder. Add a connector when the Desktop Agent needs to reach an external tool or system.
Yes. Think-Act is free to install and try, including local MCP support within the free-plan limits. Review the Think-Act downloads page for current system requirements, or compare Pro and Business plans when you need higher limits or team features.
Start with writing and OCR. Add one trusted MCP server when you have a real task that requires it. Keep write actions behind approval. Disable what you are not using.