Fascia Mcp Server

io.github.orcar-studioPublished by GitHub account orcar-studiov0.1.1Updated Oct 24, 2026

Expose Fascia-deployed Tools and Entity schemas to AI agents via MCP

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.orcar-studio/fascia-mcp-server
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account orcar-studio for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.orcar-studio%2Ffascia-mcp-server.svg)](https://sourceweft.com/mcp/io.github.orcar-studio%2Ffascia-mcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that exposes Tools and Entity schemas deployed in a Fascia workspace to AI agents.

What you can do: Expose Fascia-deployed Tools to the assistant as callable MCP tools
Expose Entity schemas from the Fascia workspace so the assistant can see their structure
Connect the assistant to a specific Fascia workspace through its API key and base URL
When to use it: Use it when your team builds and deploys Tools and Entity schemas in Fascia and you want an AI assistant to discover and use them from a desktop client.
Requirements: Runs as a local process over stdio, installed from the npm package @fascia-run/mcp-server (Node.js). Requires a Fascia workspace API key in FASCIA_API_KEY, obtained from the Fascia app settings, and optionally a custom API base URL in FASCIA_API_URL. Network access to the Fascia API is needed.

Before you install

The server needs a Fascia workspace API key (FASCIA_API_KEY), which grants access to that workspace; keep it out of shared configs and logs. Tools exposed from Fascia may act on workspace data, so review what each deployed Tool does before letting an assistant call it. Requests go to the Fascia API at the configured base URL.

Installation

In SourceWeft

Open Fascia Mcp Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.