A plugin gives the agent more tools. A connector is a plugin whose tools reach another service, for example a 3D model generator or your team's tracker. Plugins work with every AI choice: the Graspable agent, Claude Code and Codex get the same tools.
Plugins work for projects on your computer. Cloud projects do not use them yet.
Add one
Open Settings → Plugins and connectors.
- Switch on a connector that comes with Graspable. Tick it, fill in what it asks for and choose Save. Then choose Test: it connects once and tells you how many tools it found.
- Add an MCP server. Open Add a plugin or an MCP server, give it a name and its
httpsaddress, and tick needs an access token if it does. Any service with an MCP server works this way. - Add a plugin. Paste the path of its folder on your computer, or the
httpsaddress of its manifest.
World Labs generates worlds with your own World Labs account. Meshy and Tripo generate and process models with your accounts at those services. UE-MCP for Unreal Engine gives the agent more tools in the Unreal Editor; it comes with the Pro plan and higher, works for Unreal projects only and has no Test button, because it needs a project. See Native XR.
Secret values such as API keys are kept in your computer's keychain. They are handed to a run when it starts and are never written to a file by Graspable.
Characters and models
In Settings → Plugins and connectors, enable Meshy or Tripo, enter your API key, then Save and Test. Testing lists the available tools; it does not generate a model or validate your balance. Generation and rigging use the provider's balance and follow your Graspable approval settings.
With Meshy connected, ask the agent to find your completed API models, generate a character, rig it, or apply animation clips. Meshy's automatic rigging is intended for textured humanoids with clearly defined limbs. A generated model still needs a visual check for deformation, scale and foot contact. See Meshy's rigging requirements.
With Tripo connected, ask the agent to create a character with a rigging step, or retrieve a completed API task by its ID. Its connector can inspect the CLI's recent task history; that is not a browser of your complete Tripo website library. Tripo offers multiple rig types, but suitability depends on the model and processing options. See Tripo rigging.
Bring a model you already have
- Export the model from its service, including its skeleton and animation clips. GLB is the simplest choice for web and XR projects because it can keep geometry, textures, skins and animations in one file. FBX is also useful for native engine projects.
- In your desktop project, open Assets → Add and choose the exported file. Graspable keeps the original and copies it into your project. An existing file with the same name is preserved; a number is added to the new filename.
- Select a GLB or glTF model in Assets to see its skin and joint counts, morph targets and named animation clips. The small preview shows the model at rest. Ask the agent to place the model in the scene and wire the clips to the behavior or sequence you want.
For a .gltf export, keep its buffer and texture files beside it in the folders supplied by the exporter. Add the .gltf file; Graspable copies those local dependencies together into a model folder. References outside that folder or to remote addresses are refused. Export a GLB if the exporter uses a more complicated layout. Imports are limited to 300 MB, including glTF dependencies.
Meshy API assets and the website's My Assets are separate. To bring a website model into Graspable, export it from Meshy and add the file; connecting an API key does not synchronize that library. See Meshy's account and download notes.
Existing exports from Luma Genie and other services can be added the same way. There is no Genie generation or account-library connector here: Luma's currently documented public API provides image and video generation. A static model export does not gain a rig just by importing it. USD, USDA, USDC and USDZ assets open the OpenUSD inspector, which can build a GLB preview of supported scene data while preserving the original files.
The connectors give the agent provider tools. There is no automatic library synchronization, universal retargeter, or skeletal clip editor in the animation timeline yet. Downloaded provider assets remain editable project files; keep a copy before remeshing a rigged character, because remeshing can discard its rig.
What the agent may do with them
Every plugin tool counts as reaching outside your project. With the default approval setting the agent asks you before it uses one. A plugin can mark a tool as read-only; those run without asking. See Approvals and safety.
The tools appear in a run's Context list under Plugins, together with any plugin that could not connect and why.
Connected services
Open Settings → Connected services to connect your accounts of other services: Notion, Slack, GitHub, Google Sheets, Linear and thousands more. Find the service, choose Connect, and sign in at the service itself in your browser. When you come back, the service is in the list.
The same list is on the website: sign in and open Account → Connectors to connect a service or disconnect one.
Then add it to the projects that need it. In a project, next to the box where you write to the agent, choose Connect apps and pick from the services you connected; Connect another app in that list takes you to Settings. From your next request on, the agent has that service's tools in this project: it can read a Notion page, post to Slack or open a GitHub issue while it builds. Remove a service from the project with the × beside its name; it stays connected for your other projects.
- You sign in at the service. Graspable never sees your password, and the sign-in is kept by Pipedream, the company that runs the connections for Graspable.
- A project gets only the services you added to it, so the agent is not handed tools the project has no use for.
- The tools reach only the accounts you connected yourself. Disconnect (the bin icon) removes the sign-in for good.
- Like every tool that reaches outside your project, the agent asks before it uses one. See Approvals and safety.
- Connected services come with the Builder plan and higher; see Plans and billing. They work for projects on your computer.
- A published app can use a connected service too, as you, through a grant you make for that app: see Connectors in your app.
Write a plugin
A plugin is a folder with a file named graspable-plugin.json:
{
"name": "meshes",
"title": "Meshes",
"version": "1.0.0",
"kind": "connector",
"description": "Generate 3D models from a description.",
"fields": [
{ "name": "API_KEY", "label": "API key", "secret": true, "url": "https://example.com/keys" }
],
"mcp": {
"type": "http",
"url": "https://mcp.example.com/v1",
"headers": { "Authorization": "Bearer ${API_KEY}" }
},
"risk": { "search_models": "read" }
}
| Key | Meaning |
|---|---|
name |
Lowercase letters, digits and dashes. Tools are offered as <name>__<tool>. |
kind |
plugin or connector. |
fields |
What the person fills in. secret: true goes to the keychain. default and optional are allowed. |
mcp |
Where the tools come from. ${NAME} is replaced with a field's value. |
risk |
What a tool can do: read, write, exec or external. Tools not listed are external and ask first. |
skills |
A folder of skills the plugin brings. Default: skills. |
The mcp part has two forms.
An address. type: "http" with an https url and optional headers. Two extras:
oauth:{ "tokenUrl", "clientId", "clientSecret" }gets a bearer token with the client-credentials flow before connecting.each:{ "name": "APP", "from": "APPS" }opens one connection for every comma-separated item of the fieldAPPS, with the item available as${APP}.
A program. type: "stdio" with a command, args and env. Graspable starts it in the plugin's folder and talks MCP over its standard input and output. node, npx and bun work even when Node.js is not installed, because Graspable's built-in runtime answers to those names.
{ "mcp": { "type": "stdio", "command": "node", "args": ["server.js"], "env": { "API_KEY": "${API_KEY}" } } }
A plugin that starts a program must be added from a folder on your computer. A manifest added from an address may only point at an MCP address.
From a terminal
grasp plugins
grasp plugins add ./meshes
grasp plugins on meshes
For a run started with grasp run, secret fields come from the environment: GRASPABLE_PLUGIN_<NAME>_<FIELD>, for example GRASPABLE_PLUGIN_MESHES_API_KEY. See CLI.