Tools Overview

#maivn-tools

Give your agents real-world reach. maivn-tools is the official connector layer for the mAIvn Python SDK: it turns external services (Gmail, Slack, GitHub, Stripe, Postgres, and 170+ more) into tools an Agent or Swarm can call, with one line of registration each. Bring an API of your own, and the generic adapters expose it the same way.

Warning: Experimental — use with care. maivn-tools is in early development. Connectors and toolsets are exercised against a mock transport in CI, but most have not yet been validated end-to-end against live third-party provider APIs. Request shapes, behavior, and the public surface may change between releases. Test against your own provider accounts before relying on any connector in production, and please report issues.

It ships in three parts:

• A small, public connector kernel (Tier 0) with auth strategies, an HTTP runtime, audit events, file primitives, and a test transport.
• Generic adapters that turn HTTP, OpenAPI, GraphQL, webhooks, and MCP servers into Agent- and Swarm-ready tools without writing any per-provider glue.
• Provider toolsets (GmailToolSet, SlackToolSet, GitHubToolSet, StripeToolSet, AnthropicToolSet, and friends) declared with the @toolset / @toolify decorators from maivn. Register a whole toolset (or a filtered subset) on an Agent with one call.

New here? Start with the Quickstart, skim the Architecture to see how the layers fit, then jump to the connector category below that matches the service you want to reach.

Install the package. It pulls the SDK automatically:

pip install maivn-tools

maivn-tools depends on maivn directly, so a single install command gives you the SDK and connector code. Optional drivers and provider credentials are still required for the connectors that use them. Python 3.12+ is required. The package is not exposed as a maivn[tools] extra; doing so creates circular release-time coupling between the SDK and the add-on, which is why maivn[studio] was retired in 0.3.0 as well.

#Foundations

#Connectors by category

#Files, storage & local data

#Email & calendar

#Productivity & documents

#Collaboration & messaging

#Project & developer tools

#CRM & business

#Databases & warehouses

#Analytics & BI

#HR & people ops

#Marketing & ads

#Payments, finance & commerce

#AI providers

#Cloud & observability

#Identity & security

#Breadth & automation

#Governance

#Stability

maivn-tools is in active development. Public imports rooted at maivn_tools.* follow semantic versioning. Modules under _internal or explicitly marked experimental may change between minor releases.

Connectors are tested against an in-process mock transport (see Testing connectors); most have not yet been validated end-to-end against live third-party provider APIs. Treat the provider toolsets as experimental until you have verified them against your own accounts, and please report any discrepancies.

#License

Apache-2.0. See LICENSE.

• Files from custom toolsets: generic attachment custody and optional custom editable sources.

Ordinal summary refs such as message_1 label items in one response. They are not persistent provider IDs. Request include_ids=True when a follow-up needs an ID, and retain the required parent context (repository, mailbox, project or account).

#Result references and registration filters

Ordinal references such as customer_1 identify items within one response. They are not provider IDs and can change across pages or calls. Request include_ids=True when a follow-up tool needs an ID, and keep any required parent context (workspace, repository, drive or account).

Permission and destructive tags describe tools; they do not restrict a provider token. Excluding destructive still leaves ordinary WRITE methods available. Use an explicit method allowlist and restricted credentials for read-only agents.