What is the key difference between SEFAZ: PR and SEFAZ SP: NFE?

SEFAZ: PR belongs to the Developer Tools category with local stdio execution, while SEFAZ SP: NFE belongs to the Developer Tools category with local stdio execution.

How do I install SEFAZ: PR or SEFAZ SP: NFE in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are SEFAZ: PR and SEFAZ SP: NFE free or paid?

SEFAZ: PR operates under a Free / Open Source model (No auth required). SEFAZ SP: NFE operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

SEFAZ: PR lists 0 tools with 0 views and 0 GitHub stars. SEFAZ SP: NFE lists 0 tools with 0 views and 0 GitHub stars.

Can I use both SEFAZ: PR and SEFAZ SP: NFE together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

SEFAZ: PR vs SEFAZ SP: NFE

In-depth architectural comparison of the SEFAZ: PR and SEFAZ SP: NFE MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

SEFAZ: PR

Developer Tools · Local stdio

Quality: 29/100 (Emerging) | Auth: No auth required

SEFAZ SP: NFE

Developer Tools · Local stdio

Quality: 29/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose SEFAZ: PR if you need specialized Developer Tools tools running via a local process. Choose SEFAZ SP: NFE if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose SEFAZ: PR when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore SEFAZ: PR Details

Choose SEFAZ SP: NFE when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore SEFAZ SP: NFE Details

Feature & Specification Comparison

Specification	SEFAZ: PR Developer Tools	SEFAZ SP: NFE Developer Tools
Summary	SEFAZ: PR, official-source lookup. Platform-hosted, pay per query with prepaid credit.	SEFAZ SP: NFE, official-source lookup. Platform-hosted, pay per query with prepaid credit.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

SEFAZ: PR Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

SEFAZ SP: NFE Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

SEFAZ: PR Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sefaz-pr": {
      "command": "npx",
      "args": [
        "-y",
        "sefaz-pr"
      ]
    }
  }
}

SEFAZ SP: NFE Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sefaz-sp-nfe": {
      "command": "npx",
      "args": [
        "-y",
        "sefaz-sp-nfe"
      ]
    }
  }
}

Frequently Asked Questions

SEFAZ: PR is categorized under Developer Tools and uses a local stdio subprocess. In contrast, SEFAZ SP: NFE belongs to Developer Tools using local stdio subprocess. Select SEFAZ: PR when you need capabilities focused on developer tools and SEFAZ SP: NFE when you require tools for developer tools.

More alternatives to SEFAZ: PR More alternatives to SEFAZ SP: NFE Developer Tools category hub