chore: update keycard mentions

Author: kamil-keycard

DEVELOPER.md

@@ -1,6 +1,6 @@
 # Developer Guide
 
-This guide covers development workflows, architecture decisions, and contribution guidelines for the KeyCard AI Python SDK.
+This guide covers development workflows, architecture decisions, and contribution guidelines for the Keycard Python SDK.
 
 ## Getting Started
 

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 KeycardAI
+Copyright (c) 2024 Keycard
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -1,6 +1,6 @@
-# KeyCard Python SDK
+# Keycard Python SDK
 
-A collection of Python packages for KeyCard services, organized as a uv workspace.
+A collection of Python packages for Keycard services, organized as a uv workspace.
 
 ## Requirements
 
@@ -58,7 +58,7 @@ or
 uv add keycardai-mcp
 ```
 
-### Get Your KeyCard Zone ID
+### Get Your Keycard Zone ID
 
 1. Sign up at [keycard.ai](https://keycard.ai)
 2. Navigate to Zone Settings to get your zone ID
@@ -78,7 +78,7 @@ mcp = FastMCP("My Secure MCP Server")
 def my_protected_tool(data: str) -> str:
     return f"Processed: {data}"
 
-# Add KeyCard authentication
+# Add Keycard authentication
 access = AuthProvider(
     zone_id="your_zone_id_here",
     mcp_server_name="My Secure MCP Server",
@@ -141,7 +141,7 @@ or
 uv add keycardai-mcp-fastmcp
 ```
 
-### Get Your KeyCard Zone ID
+### Get Your Keycard Zone ID
 
 1. Sign up at [keycard.ai](https://keycard.ai)
 2. Navigate to Zone Settings to get your zone ID
@@ -154,7 +154,7 @@ uv add keycardai-mcp-fastmcp
 from fastmcp import FastMCP, Context
 from keycardai.mcp.integrations.fastmcp import AuthProvider
 
-# Configure KeyCard authentication
+# Configure Keycard authentication
 auth_provider = AuthProvider(
     zone_id="your-zone-id",  # Get this from keycard.ai
     mcp_server_name="My Secure FastMCP Server",
@@ -181,7 +181,7 @@ if __name__ == "__main__":
 from fastmcp import FastMCP, Context
 from keycardai.mcp.integrations.fastmcp import AuthProvider, AccessContext
 
-# Configure KeyCard authentication
+# Configure Keycard authentication
 auth_provider = AuthProvider(
     zone_id="your-zone-id",
     mcp_server_name="My Secure FastMCP Server",
@@ -228,13 +228,13 @@ Configure the remote MCP in your AI client, like [Cursor](https://cursor.com/?fr
 }
 ```
 
-### 🎉 Your MCP server is now protected with KeyCard authentication! 🎉
+### 🎉 Your MCP server is now protected with Keycard authentication! 🎉
 
 ## Features
 
 ### Delegated Access
 
-KeyCard allows MCP servers to access other resources on behalf of users with automatic consent and secure token exchange.
+Keycard allows MCP servers to access other resources on behalf of users with automatic consent and secure token exchange.
 
 #### Setup Protected Resources
 
@@ -246,7 +246,7 @@ KeyCard allows MCP servers to access other resources on behalf of users with aut
 
 ## Overview
 
-This workspace contains multiple Python packages that provide various KeyCard functionality:
+This workspace contains multiple Python packages that provide various Keycard functionality:
 
 - **keycardai-oauth**: OAuth 2.0 implementation with support for RFC 8693 (Token Exchange)
 - **keycardai-mcp**: Core MCP (Model Context Protocol) integration utilities for standard MCP servers

docs/docs.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://mintlify.com/docs.json",
-  "name": "KeyCard Python SDK",
-  "description": "Python SDK for KeyCard OAuth 2.0 and Model Context Protocol (MCP) integration.",
+  "name": "Keycard Python SDK",
+  "description": "Python SDK for Keycard OAuth 2.0 and Model Context Protocol (MCP) integration.",
   "theme": "linden",
   "colors": {
     "primary": "#5B5BD6",

docs/examples/dynamic-client-registration.mdx

@@ -1,6 +1,6 @@
 ---
 title: "Dynamic Client Registration"
-description: "How to register OAuth clients dynamically using the KeyCard OAuth SDK"
+description: "How to register OAuth clients dynamically using the Keycard OAuth SDK"
 ---
 
 # Dynamic Client Registration

docs/examples/fastmcp-integration.mdx

@@ -1,11 +1,11 @@
 ---
 title: "FastMCP Integration"
-description: "How to use KeyCard OAuth with FastMCP servers for automated token exchange"
+description: "How to use Keycard OAuth with FastMCP servers for automated token exchange"
 ---
 
 # FastMCP Integration
 
-Simple examples showing how to use KeyCard OAuth components with FastMCP for automated token exchange.
+Simple examples showing how to use Keycard OAuth components with FastMCP for automated token exchange.
 
 ## Installation
 
@@ -15,7 +15,7 @@ uv add keycardai-mcp-fastmcp keycardai-oauth fastmcp
 
 ## Core Components
 
-### 1. KeyCard Auth Provider
+### 1. Keycard Auth Provider
 
 Handles JWT authentication and user verification:
 

docs/project/decisions/0001-use-uv-workspaces-for-package-management.mdx

@@ -1,6 +1,6 @@
 ---
 title: "ADR-0001: Use uv Workspaces for Multi-Package Development"
-description: "Architecture decision to use uv workspaces for managing multiple related packages in the KeyCard Python SDK"
+description: "Architecture decision to use uv workspaces for managing multiple related packages in the Keycard Python SDK"
 ---
 
 # ADR-0001: Use uv Workspaces for Multi-Package Development
@@ -11,7 +11,7 @@ description: "Architecture decision to use uv workspaces for managing multiple r
 
 ## Context
 
-KeycardAI is developing a Python SDK that will consist of multiple related packages (starting with keycard-oauth). We need to decide on the optimal development and packaging strategy that balances:
+Keycard is developing a Python SDK that will consist of multiple related packages (starting with keycard-oauth). We need to decide on the optimal development and packaging strategy that balances:
 
 - Development velocity and convenience
 - Dependency management and consistency
@@ -26,7 +26,7 @@ KeycardAI is developing a Python SDK that will consist of multiple related packa
 
 ## Decision
 
-We will use **uv workspaces** for multi-package development in the KeycardAI Python SDK.
+We will use **uv workspaces** for multi-package development in the Keycard Python SDK.
 
 ### Key Implementation Details
 

docs/project/decisions/0002-modular-package-structure-for-minimal-dependencies.mdx

@@ -11,7 +11,7 @@ description: "Architecture decision to structure the SDK as multiple focused pac
 
 ## Context
 
-As the KeycardAI Python SDK grows to support multiple integration patterns and frameworks, we need to ensure that consumers only install the dependencies they actually need. Different users have different requirements:
+As the Keycard Python SDK grows to support multiple integration patterns and frameworks, we need to ensure that consumers only install the dependencies they actually need. Different users have different requirements:
 
 - **Core OAuth users** only need basic OAuth 2.0 client functionality
 - **FastMCP users** want OAuth integration with FastMCP servers but don't need other MCP implementations
@@ -36,7 +36,7 @@ This creates several problems:
 
 ### Real-World Example: FastMCP Integration
 
-Consider a user who wants to add KeyCard OAuth to their existing FastMCP server:
+Consider a user who wants to add Keycard OAuth to their existing FastMCP server:
 
 ```python
 # With modular structure ✅
@@ -50,7 +50,7 @@ The modular approach installs only the essential dependencies, while a monolithi
 
 ## Decision
 
-We will structure the KeycardAI Python SDK as **multiple focused packages** rather than a single monolithic package, following the principle of **minimal necessary dependencies**.
+We will structure the Keycard Python SDK as **multiple focused packages** rather than a single monolithic package, following the principle of **minimal necessary dependencies**.
 
 ### Package Structure
 

docs/project/decisions/0003-use-commitizen-for-commit-validation-and-changelog-management.mdx

@@ -11,7 +11,7 @@ description: "Architecture decision to use Commitizen for standardizing commit m
 
 ## Context
 
-The KeycardAI Python SDK is structured as a monorepo with multiple packages (oauth, mcp, mcp-fastmcp) that need independent versioning and changelog management. We need a solution that:
+The Keycard Python SDK is structured as a monorepo with multiple packages (oauth, mcp, mcp-fastmcp) that need independent versioning and changelog management. We need a solution that:
 
 - **Standardizes commit messages** across the entire development team
 - **Automates changelog generation** from commit history
@@ -39,7 +39,7 @@ Without standardized commit messages and automated changelog generation:
 
 ## Decision
 
-We will use **Commitizen** for commit message standardization and changelog generation across the KeycardAI Python SDK monorepo.
+We will use **Commitizen** for commit message standardization and changelog generation across the Keycard Python SDK monorepo.
 
 ### Key Implementation Details
 

docs/project/decisions/README.md

@@ -1,6 +1,6 @@
 # Architecture Decision Records (ADRs)
 
-This directory contains Architecture Decision Records for the KeycardAI Python SDK project.
+This directory contains Architecture Decision Records for the Keycard Python SDK project.
 
 ## What are ADRs?