Studio By Ai21 Labs
AI21 Studio provides API access to Jurassic-1 large-language-models. Our models power text generation and comprehension features in thousands of live applications.
Verdict
Common use cases
- Compare contract versions to spot edits
- Build custom assistants for internal workflows
- Classify support tickets by required parts
- Verify URLs before embedding in docs
- Automate compliance checks for grant IDs
Integration
- Vendor
- Studio By Ai21 Labs
- Category
- other
- Auth
- API_KEY
- Tools
- 50
- Composio slug
studio_by_ai21_labs
Tools
- Check Can Iframe
Tool to check if a URL can be embedded in an iframe. Use when you need to verify iframe compatibility before embedding external content.
- Check Kirsh Grant Compliance
Tool to check compliance for Kirsh grant IDs. Use when you need to verify compliance status for one or more grants.
- Compare Text
Tool to compare two text strings and identify differences. Use when you need to analyze changes between an original text and its modified version.
- Create Aftersales Parts Classification Batch
Tool to create a batch job for Fnac Aftersales parts classification. Use when you need to classify multiple aftersales cases to determine which parts are needed for repairs.
- Create Assistant
Tool to create a new AI assistant in AI21 Studio. Use when you need to set up a new assistant with custom configuration, tools, and behavior.
- Create Assistant Plan
Tool to create a new plan for an AI21 Studio assistant. Use when you need to add a new plan with Python code to an assistant.
- Create Assistant Route
Tool to create a new route for an AI21 Studio assistant. Use when you need to define a new conversational path or query pattern for an assistant.
- Create Demo
Tool to create a new demo in AI21 Studio. Use when you need to set up a new demo with specified visibility and status.
- Create Kirsh Grant Compliance Preview
Tool to preview grant compliance for Kirsh grants. Use when you need to check compliance status for specific grant IDs.
- Create MCP Storage
Tool to create MCP (Model Context Protocol) storage in AI21 Studio. Use when you need to register and configure an MCP server connection for your workspace.
- Create Secret
Tool to save a secret in AI21 Studio. Use when you need to securely store sensitive information like API keys or passwords.
- Create Website Connector
Tool to create a website connector in AI21 Studio. Use when you need to index website content via sitemap or specific URLs for RAG or grounding purposes.
- Delete Assistantdestructive
Tool to delete an assistant by its unique ID. Use when you need to permanently remove an assistant from the system.
- Delete Assistant Routedestructive
Tool to delete a route from an AI21 Studio assistant. Use when you need to remove a routing configuration from an assistant.
- Delete Demodestructive
Tool to delete a demo by its unique ID. Use when removing a specific demo from AI21 Studio.
- Delete MCP Storagedestructive
Tool to delete an MCP (Model Context Protocol) storage configuration by its unique ID. Use when you need to permanently remove an MCP server configuration from AI21 Studio.
- Delete Secretdestructive
Tool to delete a secret by its unique ID. Use when you need to permanently remove a secret from AI21 Studio.
- Delete Website Connectordestructive
Permanently delete a website connector by its unique identifier. Use when you need to remove a website connector that is no longer needed.
- Download Modified Document
Tool to download a modified document from AI21 Labs Studio. Use when you need to generate and download a document with specific content and filename.
- Generate Requirements
Tool to generate requirements from a query or task description. Use when you need to break down a high-level task into specific requirements.
- Generate Thread Name
Tool to generate a thread name from a query or conversation context. Use when you need to create a descriptive title for a conversation thread.
- Get Assistant
Tool to retrieve an assistant by its unique identifier. Use when you need to get details about a specific assistant including its configuration, tools, and settings.
- Get Assistant Route
Tool to retrieve details of a specific route for an AI21 Studio assistant. Use when you need to get information about a particular route configuration.
- Get Assistants By MCP
Tool to retrieve all assistants associated with a specific MCP (Model Context Protocol) storage configuration. Use when you need to list assistants that are connected to a particular MCP server.
- Get Batch Prediction Status
Tool to check the status of a Fnac Aftersales parts classification batch prediction job. Use when you need to monitor the progress or retrieve results of a previously submitted batch.
- Get Demo
Tool to retrieve a demo by its unique ID. Use when you need to fetch details about a specific demo including its name, status, visibility, and configuration.
- Get Library Batch Status
Tool to get the ingestion status of a library batch. Use when you need to check the processing status of documents in a batch upload.
- Get MCP Storage
Tool to retrieve a specific MCP (Model Context Protocol) storage configuration by its unique ID. Use when you need to get details about a particular MCP server including its URL, label, authentication settings, and allowed tools.
- Get Output Explanation
Tool to get output explanation for an execution (cached or generated). Use when you need to retrieve or regenerate the explanation for a specific execution. Set force_regenerate to true to bypass cache.
- Get Plan
Tool to retrieve a specific plan from an AI21 Studio assistant. Use when you need to fetch details of a plan by its ID.
- Get Website Connector By ID
Tool to retrieve details of a specific website connector by its ID. Use when you need to fetch information about a website connector in AI21 Studio.
- Get Website Connector Status
Tool to retrieve the status of a website connector ingestion. Use when you need to check the processing status of a website that was added to AI21 Studio.
- Get Website Connector URL Status
Tool to retrieve the status of a specific URL in the website connector. Use when you need to check the processing status of a URL that was previously ingested.
- Grant Kirsh Metadata
Tool to retrieve Kirsh grant metadata by grant ID. Use when you need to fetch grant information including grant name and organization details.
- Ingest Website Connector
Tool to ingest website content via sitemap URL in AI21 Studio. Use when you need to process and index website pages from a sitemap for RAG, grounding, or document analysis purposes.
- Ingest Website Connector URL
Tool to ingest a website URL into AI21 Studio's website connector. Use when you need to add a specific URL to be processed and indexed by the website connector for RAG or grounding.
- Kirsh Grant Metadata Preview
Tool to retrieve grant metadata from the Kirsh preview endpoint. Use when you need to fetch grant information including grant name and associated organization details.
- List Assistants
Tool to retrieve all assistants from AI21 Studio. Use when you need to list available assistants, optionally filtered by workspace IDs.
- List Available Models
Tool to retrieve all available models from AI21 Studio settings. Use when you need to list models that are available for use in the workspace.
- List Demos
Tool to retrieve all demos from AI21 Studio. Use when you need to list all available demos including their names, statuses, visibility settings, and configurations.
- List Library Files
Tool to list files in the workspace library with optional filtering. Use to retrieve file metadata, search by name/path/status/labels, or paginate through library contents.
- List MCP Storage
Tool to retrieve all MCP (Model Context Protocol) storage configurations from AI21 Studio. Use when you need to list available MCP servers and their configurations, optionally filtered by workspace ID.
- List Models
Tool to retrieve information about all available AI21 models. Use when you need to list models with their specifications, pricing, and capabilities.
- List Plans
Tool to list all plans for a specific assistant. Use when you need to retrieve the plans associated with an assistant ID.
- List Secrets
Tool to retrieve all secrets from AI21 Studio secret storage. Use when you need to list stored secrets and their metadata.
- List Website Connectors
Tool to retrieve website connector information from AI21 Studio. Use when you need to get details about configured website connectors.
- List Workspace Models
Tool to retrieve all workspace models by organization from AI21 Studio. Use when you need to list available models for the workspace.
- Modify Assistant
Tool to modify an existing AI21 Studio assistant. Use when you need to update assistant properties like name, description, models, system prompt, or configuration. At least one field must be provided to update. All fields except assistant_i
- Modify Assistant Plan
Tool to modify an existing assistant plan in AI21 Studio. Use when you need to update the code or schemas of a plan.
- Modify Assistant Route
Tool to modify an existing route within an assistant. Use when you need to update the description or examples of a specific route in an AI21 Studio assistant.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to Integrations. 2. Search for 'Studio by AI21 Labs' and click Connect. 3. You'll be prompted to enter an API key — generate one from your AI21 Studio dashboard under API Keys. 4. Paste the key into Switchy and click Authorize. 5. Once connected, open any Space and type '@Studio' to confirm the integration appears in the mention menu. 6. Test the connection by asking '@Studio create an assistant with the name TestBot' — if it returns a success message or assistant ID, you're live. 7. To invoke other tools, reference them by name in your prompt (e.g. '@Studio compare these two paragraphs').
What teammates see: by default, memories from Studio By Ai21 Labs are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Compare Document Versions
@Studio compare the following original text with the revised version and list all changes: [paste original] vs [paste revised].Open in a Space →
Create a Custom Assistant
@Studio create an assistant named 'SupportBot' configured to answer product questions and escalate unresolved issues.Open in a Space →
Check Iframe Compatibility
@Studio check if this URL can be embedded in an iframe: [paste URL].Open in a Space →
Classify Aftersales Cases
@Studio create a batch classification job for these aftersales case IDs to determine required parts: [list IDs].Open in a Space →
Verify Grant Compliance
@Studio check compliance for these Kirsh grant IDs and report any issues: [list grant IDs].Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Studio By Ai21 Labs create a new assistant named 'Support Triage Bot' that routes customer questions to the right team based on topic
Created assistant 'Support Triage Bot' (ID: asst_7k2m9p). The assistant is configured with default routing capabilities and can be extended with custom routes to classify incoming questions by department (billing, technical, sales). Next steps: define specific routes using the route creation tool to map question patterns to team destinations. The assistant is currently in draft mode and requires at least one route before activation.
This example shows the MCP's assistant creation capability, which is the foundation for building custom AI workflows in AI21 Studio. Note that creating an assistant requires subsequent configuration (routes, plans, tools) before it becomes functional. API key must have write permissions for assistant management.
@Studio By Ai21 Labs compare the text in our current privacy policy with the draft version I just uploaded, and highlight what changed
Analyzed 2,847 words across both documents. Key differences identified: Section 3 (Data Retention) updated retention period from 24 months to 36 months; Section 5 (Third-Party Services) added two new processor names (CloudMetrics, AnalyticsPro); Section 7 (User Rights) expanded GDPR language with explicit mention of right to data portability. Minor wording changes detected in 8 additional paragraphs. Full diff shows 127 character-level changes total.
The text comparison tool excels at identifying substantive changes in documents, making it useful for version control and compliance review. Works best with plain text under 10,000 words per document. For larger documents or complex formatting, consider chunking the comparison into sections.
@Studio By Ai21 Labs check if we can safely iframe the vendor dashboard at https://dashboard.vendorco.com for our internal admin panel
Iframe compatibility check for https://dashboard.vendorco.com: NOT EMBEDDABLE. The target URL returns X-Frame-Options: SAMEORIGIN, which prevents embedding in iframes from different origins. Additionally, Content-Security-Policy header includes frame-ancestors 'self', reinforcing the restriction. Recommendation: contact VendorCo to request iframe allowlisting for your domain, or use a direct link instead of embedding.
This tool performs real-time HTTP header inspection to determine iframe compatibility, saving developers from trial-and-error embedding attempts. Useful during integration planning. Be aware that some sites may block automated checks or return different headers for authenticated vs. unauthenticated requests, so results reflect public access only.
Use-case deep-dives
When Studio wins for high-volume text comparison tasks
A 6-person content operations team at a SaaS company reviews 200+ user-submitted articles daily for policy compliance. Studio's Compare Text tool catches edits between submission drafts and published versions, while the iframe checker validates embedded media before publication. The API key auth means any team member can run checks without OAuth friction. This works until you hit specialized needs: if you're checking grant compliance (Kirsh Grant tool) or classifying repair parts (Fnac Aftersales tool), you're using vendor-specific tools that won't generalize. Studio shines when your workflow is text-diff heavy and you need fast, repeatable checks. If your team needs more than 5-6 of these 50 tools regularly, the sprawl becomes a maintenance problem. Best fit: content teams doing high-frequency text validation with occasional structured data checks.
Studio's Create Assistant tools for rapid chatbot iteration
A 3-person support team at a B2B startup wants to test conversational flows before committing to a full chatbot platform. Studio's Create Assistant, Create Assistant Plan, and Create Assistant Route tools let them prototype response logic and routing in Python without standing up infrastructure. The Create Demo tool means they can share working prototypes with stakeholders in under an hour. This is ideal for teams validating whether an assistant solves their problem before buying Intercom or Zendesk AI. The trade-off: once you prove the concept, you'll migrate to a production platform—Studio isn't built for customer-facing scale or analytics. Use this when you're in discovery mode and need to fail fast on 3-4 assistant variations in a week. If you're already committed to a support platform, skip this and use their native tools.
When Studio's batch tools handle niche regulatory checks
A 2-person compliance team at a European retailer processes 500+ warranty claims monthly, each requiring parts classification and grant verification. Studio's Create Aftersales Parts Classification Batch and Check Kirsh Grant Compliance tools automate what used to be manual spreadsheet work. The batch approach means they queue Friday's claims and review results Monday morning. This works because the tools map directly to their regulatory requirements—Fnac parts taxonomy and Kirsh grant IDs are built in. The downside: these are hyper-specific. If your compliance needs don't match these exact schemas, 48 of Studio's 50 tools are irrelevant. This is a fit when you're in a vertical where Studio has pre-built compliance tooling. Otherwise, you're paying for a Swiss Army knife when you need one blade.
Frequently asked
What does the Studio by AI21 Labs MCP do in Switchy?
It connects Switchy to AI21's development platform, letting your team build and manage AI assistants, run text comparison tasks, and execute classification jobs. You can create assistants with custom tools, define conversational routes, and check iframe compatibility for embedded content — all from Switchy's shared workspace without switching to AI21's dashboard.
Do I need an AI21 Studio account to use this MCP?
Yes. You need an active AI21 Studio account and an API key with permissions for the resources you want to access. The MCP uses API key authentication, so whoever connects it must have admin or developer access to generate keys. Free-tier keys work, but rate limits apply to assistant creation and batch jobs.
Can this MCP deploy assistants to production or only manage drafts?
It can create assistants, plans, and routes, but deployment to production endpoints depends on your AI21 Studio plan and the assistant's configuration. The MCP handles setup and testing workflows well; for production deployment and monitoring, you'll still use AI21's console or their deployment API directly.
How is this different from calling AI21's API directly in my code?
The MCP wraps 50 AI21 tools into Switchy's interface, so non-technical teammates can trigger assistant creation or text comparison without writing API calls. If your team already has API integration code, this adds no value. If you want shared access to AI21 workflows without engineering tickets, it's faster.
Who on my team should connect this MCP?
Whoever owns your AI21 Studio account and can generate API keys. That's usually a product manager, ML engineer, or technical lead. Once connected, any Switchy workspace member can use the tools within their permission scope, but the connector's API key determines what resources are accessible.