Weaviate MCP integration for AI agents.
Connect AI agents to Weaviate through 5 structured actions, including get collection, get instance metadata, and get object. Review authentication, inputs, w…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Weaviate integration exposes
The Weaviate Agent App exposes 5 provider-backed actions for data, developer tools, and ai work. Its current contract lets an authorized agent get one weaviate collection definition by collection name, including properties and vectorizer settings, get weaviate instance metadata, including version, hostname, loaded modules, and grpc message size, and get one weaviate object by collection name and uuid with optional include flags, consistency, node, and tenant routing. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Weaviate account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Weaviate capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_collectionREADGet one Weaviate collection definition by collection name, including properties and vectorizer settings.
INPUTS: className / consistency
get_instance_metadataREADGet Weaviate instance metadata, including version, hostname, loaded modules, and GRPC message size.
get_objectREADGet one Weaviate object by collection name and UUID with optional include flags, consistency, node, and tenant routing.
INPUTS: className / id / include / consistencyLevel / nodeName
list_collectionsREADList all Weaviate collection definitions currently registered in the instance schema.
INPUTS: consistency
list_objectsREADList objects from one Weaviate collection with optional paging, sorting, include flags, and tenant selection.
INPUTS: className / tenant / after / offset / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_collection
classNameREQUIRED- The Weaviate collection name to retrieve.
consistencyOPTIONAL- Whether Weaviate should proxy the schema request to the cluster leader for strong consistency.
get_object
classNameREQUIRED- The Weaviate collection name the object belongs to.
idREQUIRED- The Weaviate object UUID.
includeOPTIONAL- Additional fields to include, such as classification, vector, or interpretation.
consistencyLevelOPTIONAL- The optional consistency level query value to forward.
nodeNameOPTIONAL- The optional node name query value to forward.
list_collections
consistencyOPTIONAL- Whether Weaviate should proxy the schema request to the cluster leader for strong consistency.
list_objects
classNameREQUIRED- The Weaviate collection name to query.
tenantOPTIONAL- The tenant name to target for a multi-tenant Weaviate collection.
afterOPTIONAL- The threshold UUID to page after. Use an empty string only when intentionally following the official Weaviate after semantics.
offsetOPTIONAL- The zero-based result offset.
limitOPTIONAL- The maximum number of objects to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Collection
Get one Weaviate collection definition by collection name, including properties and vectorizer settings. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_collectionVerify with Get Instance Metadata
Get Weaviate instance metadata, including version, hostname, loaded modules, and GRPC message size. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_instance_metadataSAFETY BOUNDARY
Operate Weaviate with explicit limits
- Authorize Weaviate with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Weaviate data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Weaviate rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Weaviate task completed successfully.
CONNECTION MODEL
API key
Weaviate API key used with the Authorization Bearer header.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Weaviate.