Alibaba Cloud FC MCP Server

Created By
aliyuna year ago
Overview

what is Alibaba Cloud FC MCP Server?

Alibaba Cloud FC MCP Server is a server designed to integrate Alibaba Cloud Function Compute capabilities into agent applications that support MCP Client, such as Cursor and Cline.

how to use Alibaba Cloud FC MCP Server?

To use the MCP Server, you can either start it from an npm package or from the source code. For npm, use the command: ALIBABA_CLOUD_ACCESS_KEY_ID=${your-access-key-id} ALIBABA_CLOUD_ACCESS_KEY_SECRET=${your-access-key-secret} npx alibabacloud-fc-mcp-server. For source code, clone the repository, build it, and run the server with your credentials.

key features of Alibaba Cloud FC MCP Server?

  • Integrates with Alibaba Cloud Function Compute.
  • Supports multiple MCP Clients like Cursor and Cline.
  • Provides tools for managing functions, including creating, updating, and deleting functions.

use cases of Alibaba Cloud FC MCP Server?

  1. Deploying applications to Alibaba Cloud Function Compute.
  2. Managing serverless functions through MCP Clients.
  3. Automating cloud function operations in development workflows.

FAQ from Alibaba Cloud FC MCP Server?

  • What are the prerequisites for using the MCP Server?

You need Node.js (version 18 or above) and your Alibaba Cloud credentials.

  • Is there a recommended way to start the MCP Server?

Yes, starting from the npm package is recommended for users.

  • What permissions are required for the Alibaba Cloud credentials?

AdministratorAccess is recommended for full functionality, or specific permissions like AliyunFCFullAccess.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aliyun
Star
3
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago