How do I find my Tencent Cloud SecretId and SecretKey?

Log in to the [Tencent Cloud Console](https://console.cloud.tencent.com/), navigate to [Access Management] -> [API Key Management] to find or generate your unique SecretId and SecretKey.

An EnvId is the unique identifier for a specific CloudBase environment (e.g., development or production). You can find it in the TCB Environment Overview section of the console.

Does this server handle TC3-HMAC-SHA256 signatures?

Yes! The server automatically calculates the required Signature V3 (TC3-HMAC-SHA256) for every request using your provided SecretKey, ensuring high security for your serverless backend orchestration.

Tencent CloudBase / 腾讯云开发 TCB MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Tencent CloudBase / 腾讯云开发 TCB
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Tencent CloudBase / 腾讯云开发 TCB through the Vinkius — pass the Edge URL in the `mcps` parameter and every Tencent CloudBase / 腾讯云开发 TCB tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Tencent CloudBase / 腾讯云开发 TCB Specialist",
    goal="Help users interact with Tencent CloudBase / 腾讯云开发 TCB effectively",
    backstory=(
        "You are an expert at leveraging Tencent CloudBase / 腾讯云开发 TCB tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Tencent CloudBase / 腾讯云开发 TCB "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Tencent CloudBase / 腾讯云开发 TCB MCP Server

Empower your AI agent to orchestrate your serverless infrastructure and backend resources with Tencent CloudBase (云开发), the premier BaaS platform in China. By connecting TCB to your agent, you transform complex cloud function management, database auditing, and storage orchestration into a natural conversation. Your agent can instantly retrieve function lists, invoke cloud logic with custom data, query NoSQL collections, and monitor environment quotas without you ever needing to navigate the comprehensive Tencent Cloud Console. Whether you are managing miniapp backends or coordinating high-volume digital automation, your agent acts as a real-time serverless operations assistant, providing accurate results from a single, authorized source.

When paired with CrewAI, Tencent CloudBase / 腾讯云开发 TCB becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Tencent CloudBase / 腾讯云开发 TCB tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Function Orchestration — List cloud functions, retrieve detailed metadata, and invoke logic directly through the agent.
Database Auditing — List database collections and execute complex queries on your cloud NoSQL data.
Storage Management — List and audit storage buckets and monitor file resources within your environment.
User Management — Retrieve lists of authenticated users registered in your TCB environment.
Operational Monitoring — Verify project connectivity, active regions, and monitor free quota usage to ensure stability.

The Tencent CloudBase / 腾讯云开发 TCB MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Tencent CloudBase / 腾讯云开发 TCB to CrewAI via MCP

Follow these steps to integrate the Tencent CloudBase / 腾讯云开发 TCB MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 8 tools from Tencent CloudBase / 腾讯云开发 TCB

Why Use CrewAI with the Tencent CloudBase / 腾讯云开发 TCB MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Tencent CloudBase / 腾讯云开发 TCB through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Tencent CloudBase / 腾讯云开发 TCB + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Tencent CloudBase / 腾讯云开发 TCB MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Tencent CloudBase / 腾讯云开发 TCB for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Tencent CloudBase / 腾讯云开发 TCB, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Tencent CloudBase / 腾讯云开发 TCB tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Tencent CloudBase / 腾讯云开发 TCB against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Tencent CloudBase / 腾讯云开发 TCB MCP Tools for CrewAI (8)

These 8 tools become available when you connect Tencent CloudBase / 腾讯云开发 TCB to CrewAI via MCP:

get_environment_info

Get TCB environment details

get_function_metadata

Get function details

invoke_cloud_function

Trigger cloud function

list_auth_users

List authenticated users

list_cloud_functions

List cloud functions

list_collections

List database collections

list_tcb_buckets

List storage buckets

query_cloud_db

Query cloud database

Example Prompts for Tencent CloudBase / 腾讯云开发 TCB in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Tencent CloudBase / 腾讯云开发 TCB immediately.

"List all cloud functions in our 'prod-8821' environment."

"Query the 'Users' collection for all documents where 'status' is 'active'."

"Show me the configuration and quota usage for our TCB environment."

Troubleshooting Tencent CloudBase / 腾讯云开发 TCB MCP Server with CrewAI

Common issues when connecting Tencent CloudBase / 腾讯云开发 TCB to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Tencent CloudBase / 腾讯云开发 TCB + CrewAI FAQ

Common questions about integrating Tencent CloudBase / 腾讯云开发 TCB MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.